Wednesday, 2016-11-16

*** s3wong_ has joined #openstack-meeting-300:04
*** s3wong has quit IRC00:07
*** Ace__ has joined #openstack-meeting-300:09
*** Ace__ has quit IRC00:09
*** Ace__ has joined #openstack-meeting-300:10
*** absubram has quit IRC00:13
*** Ace__ has quit IRC00:21
*** Ace__ has joined #openstack-meeting-300:21
*** Ace__ has quit IRC00:26
*** spzala has joined #openstack-meeting-300:32
*** spzala has quit IRC00:37
*** s3wong_ is now known as s3wong00:41
*** Ace__ has joined #openstack-meeting-300:46
*** Swami has quit IRC00:46
*** amotoki has joined #openstack-meeting-300:52
*** haleyb_ has joined #openstack-meeting-300:53
*** hoangcx has joined #openstack-meeting-300:54
*** bpokorny has joined #openstack-meeting-300:55
*** amotoki has quit IRC00:57
*** haleyb_ has quit IRC00:58
*** bpokorny has quit IRC00:59
*** donghao has joined #openstack-meeting-301:09
*** tovin07_ has joined #openstack-meeting-301:14
*** rajinir has quit IRC01:16
*** bpokorny has joined #openstack-meeting-301:21
*** donghao has quit IRC01:24
*** mickeys has quit IRC01:25
*** amotoki has joined #openstack-meeting-301:29
*** zhurong has joined #openstack-meeting-301:30
*** mickeys has joined #openstack-meeting-301:32
*** bpokorny_ has joined #openstack-meeting-301:33
*** bpokorny has quit IRC01:37
*** Ace__ has quit IRC01:37
*** bpokorny_ has quit IRC01:37
*** Ace__ has joined #openstack-meeting-301:38
*** stanzgy has joined #openstack-meeting-301:38
*** tqtran has quit IRC01:41
*** huanxuan has joined #openstack-meeting-301:42
*** Ace__ has quit IRC01:42
*** donghao has joined #openstack-meeting-301:47
*** donghao has quit IRC01:48
*** Ace__ has joined #openstack-meeting-301:51
*** calbers has quit IRC01:52
*** reedip_ has joined #openstack-meeting-301:57
*** calbers has joined #openstack-meeting-301:59
*** tonytan4ever has joined #openstack-meeting-302:01
*** Ace__ has quit IRC02:08
*** Ace__ has joined #openstack-meeting-302:09
*** kenji-i has quit IRC02:13
*** Ace__ has quit IRC02:13
*** Ace__ has joined #openstack-meeting-302:19
*** coolsvap has joined #openstack-meeting-302:19
*** Ace__ has quit IRC02:23
*** haleyb_ has joined #openstack-meeting-302:32
*** mickeys has quit IRC02:35
*** kenji-i has joined #openstack-meeting-302:38
*** armax has quit IRC02:44
*** haleyb_ has quit IRC02:44
*** haleyb_ has joined #openstack-meeting-302:45
*** bobmel has joined #openstack-meeting-302:47
*** bobmel has quit IRC02:51
*** s3wong has quit IRC03:03
*** baoli has joined #openstack-meeting-303:03
*** armax has joined #openstack-meeting-303:07
*** spzala has joined #openstack-meeting-303:16
*** Ace__ has joined #openstack-meeting-303:20
*** spzala has quit IRC03:20
*** Ace__ has quit IRC03:24
*** spzala has joined #openstack-meeting-303:30
*** armax has quit IRC03:39
*** sankarshan_away is now known as sankarshan03:47
*** baoli has quit IRC03:52
*** psachin has joined #openstack-meeting-303:54
*** SridarK_ has joined #openstack-meeting-303:59
*** flwang1 has quit IRC04:00
SridarK_Hi FWaas Folks04:02
*** spzala has quit IRC04:03
*** spzala has joined #openstack-meeting-304:04
*** spzala has quit IRC04:05
*** amotoki has quit IRC04:09
*** armax has joined #openstack-meeting-304:16
*** tellesnobrega has quit IRC04:17
*** Ace__ has joined #openstack-meeting-304:20
*** tonytan4ever has quit IRC04:23
*** tonytan4ever has joined #openstack-meeting-304:23
*** bks has joined #openstack-meeting-304:24
*** Ace__ has quit IRC04:25
*** tonytan4ever has quit IRC04:28
*** iyamahat has quit IRC04:31
*** yamahata has quit IRC04:32
*** krtaylor has joined #openstack-meeting-304:45
*** reedip_ has quit IRC04:59
*** reedip_ has joined #openstack-meeting-305:03
*** reedip_ has quit IRC05:08
*** bobmel has joined #openstack-meeting-305:14
*** anilvenkata has joined #openstack-meeting-305:16
*** bobmel has quit IRC05:19
*** darrenc is now known as darrenc_afk05:19
*** dims has quit IRC05:20
*** soichi has joined #openstack-meeting-305:21
*** Ace__ has joined #openstack-meeting-305:21
*** haleyb_ has quit IRC05:22
*** Ace__ has quit IRC05:26
*** prateek has joined #openstack-meeting-305:27
*** kaz_ has joined #openstack-meeting-305:28
*** flwang1 has joined #openstack-meeting-305:29
soichihi05:31
kaz_hello05:31
*** iyamahat has joined #openstack-meeting-305:32
soichi#startmeeting taas05:32
openstackMeeting started Wed Nov 16 05:32:41 2016 UTC and is due to finish in 60 minutes.  The chair is soichi. Information about MeetBot at http://wiki.debian.org/MeetBot.05:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:32
*** openstack changes topic to " (Meeting topic: taas)"05:32
openstackThe meeting name has been set to 'taas'05:32
soichihi05:32
kaz_hi05:32
soichianyone else?05:33
soichireedip?05:34
soichi#topic "Open Discussion"05:35
*** openstack changes topic to ""Open Discussion" (Meeting topic: taas)"05:35
kaz_I submitted TaaS dashboard.05:37
kaz_Please review and check it.05:38
soichi#link https://review.openstack.org/39602205:38
*** kzaitsev_mb has joined #openstack-meeting-305:38
soichikaz: Yamamoto-san gave several review comments05:39
kaz_Yes05:40
kaz_I'm prepairing to submit an updated version.05:43
soichiokay, thank you.05:47
soichiif there is no more topic, i'd like to close today's meeting.05:48
soichii'd like to propose to skip next week IRC because of national holiday in Japan05:49
soichii will announce this on the mailing list05:50
soichi#endmeeting05:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:51
openstackMeeting ended Wed Nov 16 05:51:05 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-11-16-05.32.html05:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-11-16-05.32.txt05:51
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-11-16-05.32.log.html05:51
soichibye05:51
kaz_bye05:51
*** soichi has left #openstack-meeting-305:55
*** harlowja has quit IRC05:55
*** kzaitsev_mb has quit IRC05:57
*** darrenc_afk is now known as darrenc05:57
*** flwang1 has quit IRC05:58
*** dims has joined #openstack-meeting-305:59
*** gugl has quit IRC05:59
*** irenab has joined #openstack-meeting-305:59
*** kaz_ has quit IRC06:00
*** abalutoiu has joined #openstack-meeting-306:09
*** amotoki has joined #openstack-meeting-306:10
*** lpetrut has joined #openstack-meeting-306:12
*** abalutoiu has quit IRC06:15
*** markvoelker has quit IRC06:28
*** iyamahat has quit IRC06:36
*** iyamahat has joined #openstack-meeting-306:39
*** Ace__ has joined #openstack-meeting-306:42
*** lpetrut has quit IRC06:42
*** irenab has quit IRC06:43
*** armax has quit IRC06:52
*** yamamoto_ has joined #openstack-meeting-306:53
*** liuyulong__ has joined #openstack-meeting-307:04
*** pgadiya has joined #openstack-meeting-307:04
*** liuyulong_ has quit IRC07:07
*** tuanluong has joined #openstack-meeting-307:10
*** andreas_s has joined #openstack-meeting-307:29
*** slaweq has left #openstack-meeting-307:33
*** mickeys has joined #openstack-meeting-307:36
*** lpetrut has joined #openstack-meeting-307:37
*** pcaruana has joined #openstack-meeting-307:41
*** lpetrut has quit IRC07:41
*** mickeys has quit IRC07:41
*** korzen has joined #openstack-meeting-307:43
*** matjazp has joined #openstack-meeting-307:43
*** haleyb_ has joined #openstack-meeting-308:01
*** karthiks has quit IRC08:07
*** ccamacho has joined #openstack-meeting-308:07
*** korzen has quit IRC08:18
*** haleyb_ has quit IRC08:20
*** ralonsoh has joined #openstack-meeting-308:20
*** karthiks has joined #openstack-meeting-308:22
*** paul-carlton2 has joined #openstack-meeting-308:23
*** tovin07 has quit IRC08:24
*** alexpilotti has joined #openstack-meeting-308:26
*** markvoelker has joined #openstack-meeting-308:29
*** alexpilotti has quit IRC08:30
*** alexpilotti has joined #openstack-meeting-308:30
*** markvoelker has quit IRC08:34
*** bobmel has joined #openstack-meeting-308:38
*** lpetrut has joined #openstack-meeting-308:39
*** donghao has joined #openstack-meeting-308:48
*** egallen has joined #openstack-meeting-308:55
*** andreas_s has quit IRC08:57
*** tovin07 has joined #openstack-meeting-308:57
*** paul-carlton2 has quit IRC08:58
*** andreas_s has joined #openstack-meeting-309:00
*** mickeys has joined #openstack-meeting-309:02
*** karthiks has quit IRC09:06
*** gouthamr has joined #openstack-meeting-309:13
*** kzaitsev_mb has joined #openstack-meeting-309:16
*** gouthamr has quit IRC09:17
*** gouthamr has joined #openstack-meeting-309:17
*** karthiks has joined #openstack-meeting-309:19
*** numans has joined #openstack-meeting-309:19
*** makowals has quit IRC09:22
*** yamamoto_ has quit IRC09:22
*** makowals has joined #openstack-meeting-309:22
*** tovin07 has quit IRC09:23
*** mickeys has quit IRC09:26
*** mickeys has joined #openstack-meeting-309:27
*** mickeys has quit IRC09:28
*** Ace__ has quit IRC09:35
*** paul-carlton2 has joined #openstack-meeting-309:35
*** Ace__ has joined #openstack-meeting-309:35
*** matrohon has joined #openstack-meeting-309:36
*** makowals has quit IRC09:36
*** makowals has joined #openstack-meeting-309:36
*** iyamahat has quit IRC09:39
*** gouthamr has quit IRC09:43
*** bogdando has quit IRC09:50
*** gouthamr has joined #openstack-meeting-309:50
*** bogdando has joined #openstack-meeting-309:52
*** yamahata has joined #openstack-meeting-309:55
*** tovin07_ has quit IRC09:57
*** Ace__ has quit IRC09:59
*** iyamahat has joined #openstack-meeting-310:00
*** zhurong has quit IRC10:02
*** iyamahat has quit IRC10:03
*** yamahata has quit IRC10:07
*** yamamoto has joined #openstack-meeting-310:09
*** hoangcx has quit IRC10:16
*** MarkBaker has joined #openstack-meeting-310:18
*** tuanluong has quit IRC10:22
*** korzen has joined #openstack-meeting-310:28
*** sambetts|afk is now known as sambetts10:28
*** markvoelker has joined #openstack-meeting-310:30
*** markvoelker has quit IRC10:35
*** gouthamr has quit IRC10:38
*** gouthamr has joined #openstack-meeting-310:39
*** Ace__ has joined #openstack-meeting-310:40
*** alexismonville has joined #openstack-meeting-310:43
*** Ace__ has quit IRC10:45
*** MarkBaker has quit IRC10:49
*** huanxuan has quit IRC10:53
*** tellesnobrega has joined #openstack-meeting-311:03
*** MarkBaker has joined #openstack-meeting-311:03
*** bks has quit IRC11:04
*** gouthamr has quit IRC11:07
*** alexismonville has quit IRC11:14
*** gouthamr has joined #openstack-meeting-311:27
*** Ace__ has joined #openstack-meeting-311:27
*** Ace___ has joined #openstack-meeting-311:29
*** Ace___ has quit IRC11:30
*** amotoki_ has joined #openstack-meeting-311:30
*** Ace___ has joined #openstack-meeting-311:30
*** Ace___ has quit IRC11:31
*** Ace__ has quit IRC11:31
*** amotoki has quit IRC11:33
*** yamamoto_ has joined #openstack-meeting-311:35
*** yamamoto has quit IRC11:38
*** tqtran has joined #openstack-meeting-311:41
*** tqtran has quit IRC11:45
*** alexismonville has joined #openstack-meeting-311:50
*** huanxuan has joined #openstack-meeting-311:50
*** gouthamr has quit IRC11:51
*** gouthamr has joined #openstack-meeting-311:52
*** kzaitsev_mb has quit IRC11:53
*** bogdando has quit IRC11:55
*** ianychoi has quit IRC11:55
*** bogdando has joined #openstack-meeting-311:57
*** reedip_ has joined #openstack-meeting-311:58
*** korzen has quit IRC12:02
*** korzen has joined #openstack-meeting-312:03
*** vgridnev has joined #openstack-meeting-312:03
*** alexismonville has quit IRC12:03
*** coolsvap is now known as coolsvap_12:09
*** donghao has quit IRC12:09
tdurakovjohnthetubaguy: got question on this one https://review.openstack.org/#/c/347161/4/specs/ocata/approved/live-migrate-rescued-instances.rst - we are not going to rpc.call for compute node to check that is supports rescued instances l-m, right?12:10
*** donghao has joined #openstack-meeting-312:10
johnthetubaguytdurakov: I don't think we should, need to think through that12:10
tdurakovjohnthetubaguy: because it's the thing I'm worried about12:11
*** kzaitsev_mb has joined #openstack-meeting-312:12
*** xavierr|afk is now known as xavierr12:14
*** vgridnev has left #openstack-meeting-312:14
*** stanzgy has quit IRC12:31
*** gouthamr has quit IRC12:32
*** alexismonville has joined #openstack-meeting-312:32
*** rtheis has joined #openstack-meeting-312:34
*** zhurong has joined #openstack-meeting-312:35
*** alexismonville has quit IRC12:37
*** reedip_ has quit IRC12:39
*** irenab has joined #openstack-meeting-312:39
*** irenab has quit IRC12:44
*** reedip_ has joined #openstack-meeting-312:55
*** korzen has quit IRC12:58
*** sagar_nikam has joined #openstack-meeting-312:59
*** claudiub has joined #openstack-meeting-313:00
claudiub#startmeeting hyper-v13:00
openstackMeeting started Wed Nov 16 13:00:29 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: hyper-v)"13:00
openstackThe meeting name has been set to 'hyper_v'13:00
claudiubhellou13:00
*** zhipeng has joined #openstack-meeting-313:01
claudiubanyone here for the meeting?13:01
*** vgridnev has joined #openstack-meeting-313:02
*** sagar_nikam has quit IRC13:03
*** ccamacho is now known as ccamacho|lunch13:04
*** sagar_nikam has joined #openstack-meeting-313:04
sagar_nikamHi13:04
claudiubhello :)13:04
claudiubwas waiting for more people to join13:04
sagar_nikamsorry bit late... my network went down13:05
sagar_nikamsonu will join today13:05
claudiubcool, shall we wait for him?13:05
sagar_nikamwe can start13:05
claudiubok13:06
sagar_nikamhe has some networking discussion... we can do it when he joins13:06
claudiub#topic nova status13:06
*** openstack changes topic to "nova status (Meeting topic: hyper-v)"13:06
claudiubsoo, the first ocata milestone is tomorrow13:06
claudiubwhich means spec-freeze. that means that we can only propose new features until then.13:06
claudiubthe shielded vm spec is still up, unfortunately13:07
claudiuband, I'd like to also get the hyper-v nested virtualization blueprint approved as well13:07
claudiubi'll have to send a POC patch first, though.13:08
claudiubI've already sent the patch needed for os-win13:08
sagar_nikamok13:08
claudiubcurrently writing the nova bits13:08
claudiubfrom the last summit discussion, the hyper-v nested virtualization blueprint doesn't need a spec13:09
claudiubso, yeay. :)13:09
sagar_nikamgood13:09
claudiubregarding the ovs vif plug patch, we're currently setting up the hyper-v ci to be able to run with ovs and neutron-ovs-agent instead of neutron-hyperv-agent13:10
*** prateek has quit IRC13:10
claudiubonce that's done, we'll post some ci results on the patch, and ping the nova core about the patch13:11
sagar_nikamok13:11
sagar_nikamthere were some BPs you/cloudbase proposed for the NFV usecase13:11
sagar_nikamin last cycle... what happened to those13:12
claudiubregarding the os-brick in the hyper-v driver (+ FC), it got some core review comments, they were addressed, waiting for other reviews13:12
sagar_nikamok... good13:12
claudiubbut, this week, i'm not expecting a lot of reviews, since the cores are concentrating on blueprints / spec reviews, as the deadline is tomorrow13:12
sagar_nikamhopeful FC gets merged soon13:12
claudiubyep13:12
*** pgadiya has quit IRC13:12
claudiubsagar_nikam: regarding your question, there is the hyper-v vNUMA placement blueprint13:13
claudiubwhich we've sent for review some time ago, and it is in compute-hyperv since mitaka, or liberty, if my memory doesn't fail13:13
sagar_nikamcorrect.. this is the BP.. how is it going13:14
claudiubit was reapproved for ocata13:14
claudiubbut no core reviews on the patch:13:14
sagar_nikamok13:14
claudiub#link Hyper-V: Adds vNUMA implementation https://review.openstack.org/#/c/282407/13:14
claudiubthe pci implementation got some reviews13:15
claudiubwhich needs to be addressed13:16
sagar_nikamok13:16
claudiubmoving on13:17
claudiub#topic monasca status13:17
*** openstack changes topic to "monasca status (Meeting topic: hyper-v)"13:17
claudiubso, one small patch merged since last week13:17
claudiubgot more comments, which i'll have to answer13:17
sagar_nikamfor which feature ?13:17
claudiubgot some merge conflicts, again. :)13:17
claudiubsagar_nikam: this one: https://review.openstack.org/#/c/359453/13:18
claudiubbasically, it gets some performance counters from windows13:18
sagar_nikamok13:18
sagar_nikamas on today... what shape is monasca+ hyperv... upstream13:19
sagar_nikamwhat ever is merged13:19
sagar_nikamcan it be used ?13:19
*** reedip_ has quit IRC13:19
sagar_nikamas is...13:19
sagar_nikamor more patches need to be merged... before it can get used13:19
claudiubyep, you can start monasca-agent on windows13:19
sagar_nikamand does it send the data ?13:20
sagar_nikamto monasca13:20
claudiublet me check for a second13:20
*** sankarshan is now known as sankarshan_away13:21
claudiubcheckers that have pending patches on monasca-agent: hyperv, cpu, disk; checkers that are working now: network, memory, process,  host_alive13:23
claudiuband i thought i've sent a patch for iis checker13:23
claudiuboh yeah13:24
claudiubiis works as well13:24
sagar_nikamok13:24
claudiubit was included with the wmi_checker13:24
sagar_nikamcpu and disk13:24
claudiubthe last link i've sent13:24
sagar_nikamare important13:24
sagar_nikami think we need to get it merged at the earliest13:25
claudiubthe other checkers, i haven't tested them yet. there are more than 40 checkers in total. Roland was suggesting those, as those are most commonly used.13:25
claudiubyou can see how many checkers are here: https://github.com/openstack/monasca-agent/tree/master/conf.d13:26
*** reedip_ has joined #openstack-meeting-313:27
claudiubany questions?13:27
sagar_nikamagree... i think those are the important ones... especially the disk, cpu and memory13:27
sagar_nikamno... we can move to next topic13:28
claudiub#topic open discussion13:28
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:28
claudiubsagar_nikam: so, last week I've asked if there is someone from your team that can help with getting monasca-log working on windows13:29
sagar_nikamyes... most of my team is also new to monasca13:29
sagar_nikammonasca team is in US13:30
sagar_nikamindia team does not work on it13:30
sagar_nikamanyhow let me try ... not sure though13:30
claudiubi see13:31
claudiubwell, let me know when you find out. :)13:31
sagar_nikamindia team works on nova and neutron13:31
sagar_nikamfor hyperv13:31
*** haleyb_ has joined #openstack-meeting-313:31
claudiubhave you tried hyper-v 2016 yet?13:31
sagar_nikamsonu: are you there in the meeting ?13:32
sagar_nikamclaudiub: not yet13:32
sagar_nikamwe wanted to try nano... but did not proceed much13:32
sagar_nikamas of now all our test systems are 2012 r213:32
claudiubi see13:33
claudiubdo you have any plans to upgrade in the near future?13:33
sagar_nikamwe wanted it on atleast one machine... but could not do it13:34
sagar_nikamdue to various reasons13:34
sagar_nikamas of now13:35
sagar_nikamwe support only 2012 r213:35
sagar_nikamhence getting 2016 has been a challenge in test machines13:35
claudiubhm, interesting13:35
*** amotoki_ has quit IRC13:36
sagar_nikamcloudbase supports 2016?13:36
claudiubyep13:36
sagar_nikamfor nova and neutron13:36
sagar_nikamok13:36
*** atuvenie has joined #openstack-meeting-313:36
sagar_nikamTP5 ?13:36
claudiubthat's been always a target, since it was officially announced13:36
claudiubhyper-v 2016 has been released13:36
sagar_nikamoh... missed that release announcement13:37
sagar_nikamwhen was it released13:37
claudiubyou can already download it from microsoft's site: https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-201613:38
claudiubi think it was sometime around the openstack summit in barcelona13:38
claudiubbut yeah, we do support 2016. :)13:39
*** slaweq has joined #openstack-meeting-313:39
claudiubplus, we already have a few of the 2016's features in nova, like the upgraded support for remotefx13:39
sagar_nikamok13:39
sagar_nikammay be for our next release we will try hyperv-201613:40
claudiubcool :)13:40
*** korzen has joined #openstack-meeting-313:40
claudiubany other news from your side?13:40
sagar_nikamcould you check the link i gave you last week on k8s on azure ?13:41
*** tqtran has joined #openstack-meeting-313:42
claudiubhm, wondering how they're dealing with container networking across different hosts.13:43
*** markvoelker has joined #openstack-meeting-313:44
*** zhipeng has quit IRC13:44
sagar_nikamand storage as well13:45
*** zhipeng has joined #openstack-meeting-313:45
sagar_nikameven i was curious13:45
sagar_nikamone more question which i had was... containers are only supported in 201613:45
claudiubyep13:45
sagar_nikamso does azure provision containers in 2016 ?13:45
sagar_nikamand is it stable13:46
claudiubthat, i don't know :)13:46
sagar_nikamthat can be a good indication of its stability13:46
sagar_nikamyour team is not working with MS on this ?13:46
claudiubyep, that's exactly my thought as well13:46
sagar_nikampeter is not involved13:46
sagar_nikamon containers ?13:47
sagar_nikamfrom MS13:47
*** tqtran has quit IRC13:47
*** huanxuan has quit IRC13:48
claudiubhm, i don't keep in touch with peter, only rarely13:48
sagar_nikamok13:48
claudiubsagar_nikam: any news from sonu?13:48
sagar_nikamhe wanted to join13:49
sagar_nikamhe mentioned me today as well13:49
sagar_nikamsome networking discussion with you13:49
sagar_nikamon ovs13:49
sagar_nikamhe is not in office13:49
claudiuba bug, or?13:49
sagar_nikammight have got struck in traffic13:49
sagar_nikami think he is planning to use ovs for our next release mostly probably based on mitaka or newton13:50
sagar_nikamand wanted to discuss some things on it13:50
*** gouthamr has joined #openstack-meeting-313:50
claudiubsounds good. :)13:51
sagar_nikami will request him to join next week.. or may be mail you abut it13:51
claudiubwell, he can drop me an email13:51
sagar_nikamalso if i remember right, we got the certification from MS on the OVS solution right ?13:51
claudiubyep13:51
*** liuyulong_ has joined #openstack-meeting-313:52
*** rtheis has quit IRC13:52
sagar_nikamThen i think we may mostly go with it for our next release13:53
*** zhipeng has quit IRC13:53
sagar_nikamsonu can provide more info on it13:53
*** zhipeng has joined #openstack-meeting-313:53
*** ianychoi has joined #openstack-meeting-313:53
claudiubhere's the link, where you can see the certification: https://www.windowsservercatalog.com/item.aspx?idItem=18117a8c-c7bf-f20c-9185-3a53117b9875&bCatID=163813:54
sagar_nikamanything on cluster driver ? or it is down on priority13:54
*** gouthamr has quit IRC13:54
claudiubwell, they didn't approve it for ocata13:55
claudiubwhich is sad13:55
*** liuyulong__ has quit IRC13:55
sagar_nikamok13:55
claudiubso, it got a bit down in the priority list, as they won't merge it13:55
*** rtheis has joined #openstack-meeting-313:55
*** eliqiao has quit IRC13:56
claudiubbut at least it's merged in compute hyperv13:56
sagar_nikamok fine...13:56
sagar_nikamtime almost over13:56
sagar_nikamnothing much from my side13:56
claudiubwell, i guess we can end the meeting now :)13:56
sagar_nikamthanks13:57
claudiubi'll be waiting for an email :)13:57
*** eliqiao has joined #openstack-meeting-313:57
claudiubthanks for joining, see you next week!13:57
claudiub#endmeeting13:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:57
openstackMeeting ended Wed Nov 16 13:57:55 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-11-16-13.00.html13:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-11-16-13.00.txt13:58
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-11-16-13.00.log.html13:58
*** zhipeng has quit IRC13:59
*** amotoki has joined #openstack-meeting-313:59
*** xdreamer has joined #openstack-meeting-314:00
*** reedip_ has quit IRC14:01
slaweq#startmeeting neutron_qos14:01
openstackMeeting started Wed Nov 16 14:01:38 2016 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
slaweqhello14:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:01
openstackThe meeting name has been set to 'neutron_qos'14:01
ralonsohhi14:01
slaweqI think we will wait few minutes for people14:02
*** davidsha has joined #openstack-meeting-314:02
ralonsohI read ajo and njonshon are not going to attend14:02
davidshaHi14:02
slaweqralonsoh: I think ajo will be but later14:03
ajohi o/ ;) I was supposed to have a meeting which moved, but slaweq has been preparing the meeting, I'll let him do the honours, very grateful that you could help slaweq14:03
slaweqajo: thx14:03
slaweqbut I hope You will help me with it :)14:03
ajoof course14:03
slaweqok, so can we start?14:03
*** korzen has quit IRC14:04
slaweqor we are waiting for someone else?14:04
ralonsohgo on, I think14:04
slaweqok14:04
slaweq#topic RFEs-approved14:04
*** openstack changes topic to "RFEs-approved (Meeting topic: neutron_qos)"14:04
slaweq#link https://bugs.launchpad.net/neutron/+bug/1586056 14:04
openstackLaunchpad bug 1586056 in neutron "[RFE] Improved validation mechanism for QoS rules with port types" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:04
slaweqfirst rfe-approved14:04
*** liuyulong_ has quit IRC14:05
slaweqit is still waiting for qos_notification refactor which ajo is doing:  https://review.openstack.org/#/c/351858/14:05
ajooh, a note about this one14:05
slaweqso I have nothing to add here14:05
*** liuyulong_ has joined #openstack-meeting-314:05
ajoI'm abandoning that patch in favor of:14:05
ajo    https://review.openstack.org/#/c/396651/14:06
ajo#link https://review.openstack.org/#/c/396651/14:06
ralonsohI'll review this patch today14:06
slaweqah, right, I forgot to change this link14:06
ralonsohajo's patch14:06
davidshaSame, is it meant to be work flow -1?14:06
ralonsohajo: or is still wip?14:06
ajothanks ralonsoh I will submit a new version after meeting, I was cleaning some pep8's and also adressing https://bugs.launchpad.net/neutron/+bug/1627749 partly, at the same time14:06
openstackLaunchpad bug 1627749 in neutron "qos driver api can have better error handling" [Medium,Confirmed] - Assigned to Miguel Angel Ajo (mangelajo)14:06
*** yamamoto_ has quit IRC14:06
ralonsohI'll wait14:07
ajoralonsoh, next version will be ready (just missing testing changes)14:07
slaweqajo: I will also try to review it asap14:07
ajothank you ralonsoh & slaweq14:07
*** yamamoto has joined #openstack-meeting-314:07
slaweqok so moving on, next one: https://bugs.launchpad.net/neutron/+bug/1560961 14:08
openstackLaunchpad bug 1560961 in neutron "[RFE] Allow instance-ingress bandwidth limiting" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:08
slaweqthis one depends on extended validation so is also blocked by ajo's patch :)14:08
* ajo blocks the world ':]14:08
slaweqajo: maybe not whole world but QoS part :P14:09
ralonsohas soon as ajo's patch is up, I'll review that too14:09
slaweqI saw that https://bugs.launchpad.net/neutron/+bug/1560963 is finished already14:09
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,Fix released] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:09
slaweqthx ralonsoh14:09
ajo'':]14:09
ralonsoh Minimum bandwidth support: SRIOV merged, LB under review!!14:10
ralonsohone sec14:10
ralonsohhttps://review.openstack.org/#/c/357865/14:10
slaweqI already reviewed this patch :)14:10
ralonsohslaweq is taking care of the reviews! thanks!14:10
ajo#link https://review.openstack.org/#/c/357865/14:10
ajooh right, and the OVS part was in WIP, is that correct?14:11
ralonsohyes... I don't know if I can implement it14:11
*** rtheis_ has joined #openstack-meeting-314:11
ralonsohtoo many problems14:11
slaweqralonsoh: I think I can help You on that maybe14:11
ajoralonsoh, it got more complicated than expected?14:11
ralonsohand architecture issues14:11
*** gouthamr has joined #openstack-meeting-314:11
ralonsohyes, a lot of more14:11
ajook, may be we can discuss that one for Pike and help14:11
ajolot of things in our plates14:12
ralonsohI agree14:12
*** rtheis has quit IRC14:12
slaweqralonsoh: is there patch already on gerrit?14:12
*** yamamoto has quit IRC14:12
ralonsoh#link https://review.openstack.org/#/c/318531/14:12
*** baoli has joined #openstack-meeting-314:13
ralonsohBut WIP14:13
slaweqand btw. I think that bug https://bugs.launchpad.net/neutron/+bug/1560963 shouldn't be "fix released", am I right?14:13
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,Fix released] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:13
ralonsohThe initial spec was SRIOV only14:13
ralonsohWe added LB and OVS14:13
ralonsohGo on, we can talk about this by mail14:14
slaweqok14:14
slaweqso there is one more: https://bugs.launchpad.net/neutron/+bug/157898914:14
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,Confirmed]14:14
*** baoli has quit IRC14:14
slaweqwhich is not assigned to anyone yet14:15
ajoI pushed a spec for this one: https://review.openstack.org/#/c/396297/214:15
ajoso we can discuss the technical details, and integration details with nova14:15
*** reedip_ has joined #openstack-meeting-314:15
slaweq#link https://review.openstack.org/#/c/396297/214:15
slaweqajo: ok, I will try to review it also14:15
ajowe need to involve the nova guys to have a look on the integration details, and chunk it into work items. ralonsoh took one already14:15
*** baoli has joined #openstack-meeting-314:15
ralonsohAbout this spec: should we create new specs for sub-tasks?14:16
ajoralonsoh, no, you just reference the spec from your patches14:16
ralonsohok, perfect14:16
davidshayou could file a bug to expand it right?14:16
ajobut we need a blueprint created for it14:16
ralonsohYes, I think so14:16
ajoI guess drivers could help with that.14:17
slaweqyes, agree with blueprint14:17
ajoamotoki,  ^14:17
slaweqto aggregate all such patches14:17
amotokiajo: what?14:17
ajoamotoki, : https://review.openstack.org/#/c/396297/2 this is from an approved RFE https://bugs.launchpad.net/neutron/+bug/157898914:17
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,Confirmed]14:17
*** prateek has joined #openstack-meeting-314:17
ajowe thought that the feature is complex and has many integration points with nova,14:17
ajoso we thought a spec + blueprint fits it best14:18
ajocan we get/or create ourselves the blueprint and keep rolling?14:18
amotokiajo: is there no corresponding blueprint?14:18
*** baoli_ has joined #openstack-meeting-314:18
ajoamotoki, just the approved RFE, and the spec that we decided was useful to coordinate neutron/nova and work items14:18
amotokiajo: we can create a blueprint for an approved RFE if it needs a discussion or it require a lot of effort.14:19
ajoamotoki, it's exactly that case14:19
amotokiajo: what can I help you?14:19
ajo(lot multi-cycle effort and integration with nova)14:19
ajoamotoki, can I go ahead and create the blueprint myself or should I get it asked in the drivers meeting?14:20
ajoor may be create, and just mention it in driver's ?14:20
*** lblanchard has joined #openstack-meeting-314:21
*** baoli has quit IRC14:21
amotokiyou can create a bp and let the driver team know so that they can assign a approver (= a sponsor) and set other fields.14:21
ajoI can take the approver part14:21
ajoack, thanks amotoki14:21
ajo#action ajo creates the blueprint and mentions it on drivers meeting14:21
*** tonytan4ever has joined #openstack-meeting-314:21
ralonsohthanks!14:22
slaweqok thx ajo14:22
amotokigreat!14:22
*** vgridnev has quit IRC14:22
ajothank you all14:22
slaweqanything to add?14:22
slaweqif not, we are going forward14:22
slaweq#topic RFEs14:22
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"14:22
slaweqthere is also 2 not approved rfe14:23
slaweqhttps://bugs.launchpad.net/neutron/+bug/150562714:23
openstackLaunchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,Incomplete] - Assigned to Reedip (reedip-banerjee)14:23
slaweqthis one is quite old as I remember14:23
slaweqreedip_: are You doing something with it?14:23
reedip_slaweq : Hi , I had a spec but its not yet complete14:24
reedip_its pretty slow14:24
davidshareedip_: do you have a link?14:24
reedip_davidsha : not yet, I have it in my own repo14:24
reedip_not in gerrit yet14:25
davidshareedip_: kk14:25
slaweqso there is one more: https://bugs.launchpad.net/neutron/+bug/163479814:25
openstackLaunchpad bug 1634798 in neutron "[RFE] Qos DSCP to vlan priority mapping" [Undecided,New]14:25
slaweqwhich is new14:25
*** uxdanielle has joined #openstack-meeting-314:26
slaweqI think it should be discussed on drivers meeting, right?14:26
ajoI wonder14:26
ajoif this doesn't really need to be done14:26
davidshaslaweq: its a resurrection of the vlan pcp one is it?14:26
ajoor yes14:26
ajoif what they mean is translating DSCP (send by the VM) into VLAN q priority14:27
ajobecause if what they mean is translating policies DSCP into VLAN q , they could just add a VLAN q rule, when we had that14:27
ajoI'm going to ask in the RFE14:27
slaweqajo: You mean add new qos_rule type, right?14:28
davidshaajo: I think thats it. pcp is a 0-7 value if memeory serves so you would be matching on traffic classes I guess.14:28
*** ccamacho|lunch is now known as ccamacho14:28
ajoyes, davidsha and we also have the DEI bit (drp eligible indicator)14:29
ajodrop14:29
ajobut it's 3 bits, correct14:29
ajothere was another RFE for that14:29
davidshakk, thanks.14:30
slaweqso ajo will ask in RFE about details, right?14:30
ajodone, asked14:31
slaweqthx ajo14:31
slaweqnext topic is14:31
slaweq#topic Bugs14:31
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"14:31
*** amotoki_ has joined #openstack-meeting-314:31
slaweqhttps://bugs.launchpad.net/neutron/+bug/163918614:32
openstackLaunchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed] - Assigned to Luis Tomas Bolivar (ltomasbo)14:32
slaweqI don't know if owner of this bug is here14:32
slaweqltomasbo: is it Your bug?14:32
ajoI believe ltomasbo is offline, travelling to Munich14:33
slaweqok, so next one14:33
ajoI can update14:33
ajoHe was looking into max bw compatibility with trunk ports and subports14:34
ajoand he found that subports can't be limited, because those are patch-port based14:34
ajoralonsoh,  ^ I guess that rings a bell ':D14:34
ralonsohyes, I know14:34
*** amotoki has quit IRC14:34
ajoso he was looking into the posibility of having veths dynamically created for those cases14:34
ajobut that would not work in the case of DPDK I believe14:34
ralonsohno, not in DPDK14:35
ajobut it could be useful to the container use cases14:35
ajoso, he's investigating14:35
ajo(done)14:35
slaweqthx ajo14:36
slaweqnext one: https://bugs.launchpad.net/neutron/+bug/161654714:36
openstackLaunchpad bug 1616547 in neutron "qos: rule api definition shouldn't include tenant_id" [Low,Incomplete]14:36
slaweqI don't know if this is still valid14:36
ralonsohI thinks this is solved14:36
slaweqI remember that some time ago there was some discussion about it14:36
ralonsohbut I'll check14:36
slaweqralonsoh: thx14:36
slaweqhttps://bugs.launchpad.net/neutron/+bug/162774914:36
openstackLaunchpad bug 1627749 in neutron "qos driver api can have better error handling" [Medium,Confirmed] - Assigned to Miguel Angel Ajo (mangelajo)14:36
slaweqI think ajo told at the beginning that he is working on it14:36
*** m1dev has joined #openstack-meeting-314:37
slaweqright ajo?14:37
slaweqsomething to add here?14:37
ajoyes, I'm chasing that as part of it, one sec let me push my current state14:37
*** haleyb_ has quit IRC14:37
ajoso we can show a link to what specifically I'm doing14:37
ajo#link https://review.openstack.org/#/c/396651/5/neutron/services/qos/qos_plugin.py@8414:38
ajo#link https://review.openstack.org/#/c/396651/5/neutron/services/qos/qos_plugin.py@11714:38
ajo#link https://review.openstack.org/#/c/396651/5/neutron/services/qos/qos_plugin.py@14114:39
ajoetc ..14:39
ajoat least with this, if one driver fails, (backend unavailable or something)14:39
ajowe go on and notify the others14:39
*** haleyb_ has joined #openstack-meeting-314:39
*** gouthamr has quit IRC14:39
ajoideally we could revert the DB and the plugins that worked14:39
ajobut...14:39
ajomy thinking was14:39
slaweqok, so it's related to You "big blocker" patch :)14:39
ajowhat if the other drivers won't revert or fail to revert?14:40
ajolol14:40
ajobig blocker patch is a good name for it :]14:40
slaweq:D14:40
*** sagar_nikam has quit IRC14:41
*** amotoki_ has quit IRC14:41
*** rubasov has joined #openstack-meeting-314:41
*** anilvenkata has quit IRC14:42
reedip_Hi slaweq , is there an OpenstackCLient for Neutron QoS ? Was going through https://bugs.launchpad.net/neutron/+bug/164076214:43
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:43
slaweqreedip_ just goes to next one :)14:43
ajoralonsoh, is working hard on OSC :)14:43
slaweqwhich I wanted to talk now14:43
slaweqthx reedip_14:43
ralonsoh#link https://review.openstack.org/#/c/352477/14:43
reedip_lol14:43
ralonsohwaiting for this14:43
ralonsohreviews, I mena14:44
ralonsohmean14:44
reedip_Ok, I will bring this up with the OSC :)14:44
reedip_Thanks for the patch though14:44
ralonsohthanks14:44
slaweqI think I was fixing something like that in neutronclient some time ago14:44
*** tongli has joined #openstack-meeting-314:44
reedip_slaweq : which brings up the point that the above bug would be applicable only to NeutronClient , right ?14:44
slaweqIMO only in Openstack client14:45
slaweqit should be fixed in neutronclient14:45
ralonsohI agree14:45
slaweqlet me find my patches for that14:45
reedip_slaweq : but Neutronclient is deprecated. Should we focus there ?14:45
reedip_I would prefer focussing more on OSC migration14:45
slaweqabout OSC I will check it today and will try to fix it asap14:46
slaweqI assigned me to this bug today because I remember that I was doing something like that for neutronclient some time ago14:47
slaweqhttps://review.openstack.org/#/c/327935/14:47
*** cleong has joined #openstack-meeting-314:47
slaweqthis is it14:47
slaweqreedip_: fine for You?14:47
reedip_slaweq : I just found the same patch :D14:48
slaweqnext bug is https://bugs.launchpad.net/neutron/+bug/164076714:48
openstackLaunchpad bug 1640767 in neutron "Create a qos-policy , name attribute is necessary when using openstack command line interface, and it become non essential option when I use API or curl command to create" [Undecided,Incomplete] - Assigned to Slawek Kaplonski (slaweq)14:48
slaweqI wanted to talk about this one14:48
reedip_slaweq : so -no-shared is different from the -shared option, so it means that the bug is expected ..14:48
reedip_slaweq : yes, that was another bug I was going to bring up :D14:49
*** donghao has quit IRC14:49
slaweqreedip_: there is --no-shared option added if You want to update policy to be shared=False14:49
reedip_ok14:49
slaweqit is like that instead of --shared=True or --shared=False14:49
slaweqso about https://bugs.launchpad.net/neutron/+bug/164076714:50
openstackLaunchpad bug 1640767 in neutron "Create a qos-policy , name attribute is necessary when using openstack command line interface, and it become non essential option when I use API or curl command to create" [Undecided,Incomplete] - Assigned to Slawek Kaplonski (slaweq)14:50
slaweqif You are creating QoS policy via OSC or neutronclient it must have name given14:50
*** rhochmuth has joined #openstack-meeting-314:50
slaweqbut Neutron API not require it14:50
slaweqso You can create policy without name for example with curl14:51
slaweqand now question is: which way to fix it You preffer? fix OSC and neutronclient or change neutron API?14:51
*** psachin has quit IRC14:51
slaweqajo: what do You think about it?14:51
*** zhurong has quit IRC14:51
ajohmm,14:51
ajowe can also create ports without names14:51
ajoor networks without names14:51
ralonsohIt's fine. You can use the ID14:51
ralonsohBut OSC won't allow this14:51
ajoand just depend on the ID14:51
reedip_ralonsoh : I had a similar problem with aothr bug14:52
ajoso I think there's nothing wrong with the API14:52
reedip_just a minute14:52
slaweqfor me it is something to fix on client side14:52
slaweqbut I wanted to ask about opinions14:52
ajoye, agreed14:52
ajoyeah14:52
ralonsohAgree14:52
slaweqok, thx14:52
slaweqreedip_: You wanted to add something?14:53
*** stevejims has joined #openstack-meeting-314:53
slaweqthere is also new bug: https://bugs.launchpad.net/neutron/+bug/163797714:53
openstackLaunchpad bug 1637977 in neutron "QoS API parameter name issue, max_burst_kbps should be max_burst_kbits?" [Undecided,New]14:53
ajohmm, we had that before14:54
ajomay be in form of RFE14:54
slaweqbut I think it is something what I reported few months ago and what we decided to not touch because of problems with API versions14:54
*** tomasztrebski has joined #openstack-meeting-314:54
ajonothing we can do until the day we have microversioning for API14:54
slaweqajo: it was bug reported14:54
slaweqso should we close it now?14:54
reedip_Hi, found this14:54
reedip_https://review.openstack.org/#/c/250587/14:54
reedip_I dont know, but I found amotoki's point a bit valid here14:54
reedip_comment# 414:54
slaweqor postpone it?14:54
*** andymaier has joined #openstack-meeting-314:55
ajoit's a duplicate of https://bugs.launchpad.net/neutron/+bug/150776114:55
openstackLaunchpad bug 1507761 in neutron "qos wrong units in max-burst-kbps option (per-second is wrong)" [Low,Won't fix] - Assigned to Slawek Kaplonski (slaweq)14:55
slaweqajo: exactly :)14:55
ajoI marked it as duplicate14:55
*** hosanai has joined #openstack-meeting-314:55
slaweqok, thx14:55
*** witek has joined #openstack-meeting-314:55
reedip_slaweq, ajo , ralonsoh : I dont know if you got my earlier message14:56
ralonsohreedip_: yes14:56
ralonsohone sec14:56
*** arturbasiak has joined #openstack-meeting-314:57
ralonsohreedip_ I need to read it slowly, not now14:57
*** andymaier has quit IRC14:57
slaweqyes, I will also read it later14:57
slaweq#action read comments on https://review.openstack.org/#/c/250587/14:58
slaweqok, I think that this is all bugs14:58
slaweq#topic Open discussion14:58
*** openstack changes topic to "Open discussion (Meeting topic: neutron_qos)"14:58
slaweqanyone have got anything else to add?14:58
ralonsohI'm ok14:58
slaweqwe have 2 minutes more I think14:58
reedipdamn problem with my home PC , sending the messages late14:58
*** koji has joined #openstack-meeting-314:59
*** coolsvap_ is now known as coolsvap14:59
ajoI agree with you reedip , api & client must match in capabilities14:59
reedip_just wanted to say that as per an earlier bug discussion with amotoki,  as a convention, neutron CLI requires one required argument.14:59
reedip_If all options are optional in the API level and we have 'name' field, we usually use 'name' as a required parameter.14:59
ajobut I guess it's not an easy fix on neutron client, may be14:59
slaweqok, thx everyone15:00
slaweq#endmeeting15:00
reedipajo , I think keeping it a necessary attribute doesnt break any assumptions.15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Nov 16 15:00:37 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-16-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-11-16-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-11-16-14.01.log.html15:00
ralonsohbye15:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Nov 16 15:00:52 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
slaweqbye15:00
davidshathanks, cya15:00
rhochmutho/15:01
kojio/15:01
arturbasiako/15:01
witekhello15:01
shinya_kwbto/15:01
rhochmuthAgenda has been posted at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
*** davidsha has left #openstack-meeting-315:01
hosanaio/15:01
rhochmuthOMG15:01
witek:)15:01
rhochmuthAgenda for Wednesday November 16, 2016 (15:00 UTC)15:01
rhochmuth1.Ocata-1 milestone15:01
rhochmuth2.Ocata Community Goals Acknowledgement15:01
rhochmuth1.http://governance.openstack.org/goals/ocata/remove-incubated-oslo-code.html15:01
rhochmuth3.confluent-kafka-python for monasca-common (next to kafka-python) 15:01
*** rhochmuth has quit IRC15:01
*** rhochmuth has joined #openstack-meeting-315:01
rhochmuthAnd the award for the longest agenda every goes to team Monasca15:01
tomasztrebskio/15:01
tomasztrebskiflowers, fame and glory ... :D15:02
rhochmuthWe might as well get started15:02
rhochmuth#topic Ocata-1 milestone15:02
*** rbak has joined #openstack-meeting-315:02
*** openstack changes topic to "Ocata-1 milestone (Meeting topic: monasca)"15:02
witektomorrow is Ocata 1st milestone15:02
witekshould we tag the repos?15:03
rhochmuthSure, sounds like a good idea15:03
witekok, I'll take care15:03
rhochmuthThere are already features, like the dimension names/values that are not in the python-monascaclient15:03
rhochmuthwhich we should get tagged so when devstack builds at least they show up15:04
rhochmuththanks witek15:04
*** millerthomasj has joined #openstack-meeting-315:04
rhochmuthi guess that is it on that topic15:04
rhochmuth#topic Ocata Community Goals Acknowledgement15:04
*** openstack changes topic to "Ocata Community Goals Acknowledgement (Meeting topic: monasca)"15:04
witekwe should acknowledge community-wide goals for Ocata15:05
witekthere is one actually15:05
*** jobrs has joined #openstack-meeting-315:05
tomasztrebski?15:05
witekRemove Copies of Incubated Oslo Code15:05
*** zhipeng has joined #openstack-meeting-315:05
tomasztrebskiI guess that was a problem only for client15:05
tomasztrebskiwhich was already mergde15:05
tomasztrebski*merged15:05
rhochmuthso, i'm not aware of any copies of oslo code anymore15:06
rhochmuthso, are we good on that one?15:06
rhochmuthis there a link i should be referring too?15:06
witekok, I'll update the wiki page then15:06
tomasztrebskiAFAIK we are, according to announcement only client was listed by OS as sth we need to fix15:06
*** spotz_zzz is now known as spotz15:06
witekyes, it seems we're ok on that one15:08
rhochmuthis there something we need to address with the announcemtn15:08
rhochmuthi didnt' see it15:08
witekhttp://governance.openstack.org/goals/ocata/remove-incubated-oslo-code.html15:09
witekthere is that wiki page15:09
witek monasca  Planning Artifacts:  Completion Artifacts:15:09
rhochmuthi don't see anythign listed15:10
rhochmuthfor monasca15:10
rhochmuthis there anything to do, should a completion artificat be listed15:11
rhochmuthor are we basically done15:11
witekI'm not sure15:11
witekwe could put links to completed reviews15:12
tomasztrebski+115:12
rhochmuthsounds like busy work15:12
witekthere were just 3, right?15:12
tomasztrebskiyeah15:12
tomasztrebskihttps://review.openstack.org/#/q/status:merged+project:openstack/python-monascaclient+branch:master+topic:goal-remove-incubated-oslo-code15:13
rhochmuthok, i could update that page, unless you want to witek15:15
witekyou decide :)15:15
rhochmuthi'll look into it15:16
witekthanks15:16
rhochmuthsee what is involved15:16
*** yingjun has joined #openstack-meeting-315:16
rhochmuth#topic confluent-kafka-python15:16
*** openstack changes topic to "confluent-kafka-python (Meeting topic: monasca)"15:16
rhochmuthis it really like 10X faster?15:16
tomasztrebskiaccording to the document15:17
rhochmuthi would be all for an upgrade15:17
witekat least in single node conf15:17
tomasztrebskiwe did not move with investigating/writing any code, we wanted to clarify if monasca would be interested in this15:17
rhochmuthyes interested15:17
rhochmuthneed to have joe look at this15:18
witekit is not listed in global-requirements15:18
rhochmuthhe's been measuring and followign the client that we are using15:18
tomasztrebskiwe don't have that much time to work on this, but code is WIP to make monasca-common using that library next to exisiting kafka-python15:18
rhochmuththe main reason for not upgrading is that they had some issues15:18
tomasztrebskieverything would depend on actual kafka library installed15:18
*** prateek has quit IRC15:18
tomasztrebskiso the transition if any would be smooth and not enforced15:19
tomasztrebskiplus all would end with new gate job for monasca plugin that would stack up everything with confluent-kafka15:19
rhochmuthso, could back out if there were issues?15:19
tomasztrebskithat's the rough plan for this15:19
tomasztrebskiactually you wouldn't need to back up15:19
rhochmuthhave you don't any analysis of the api or persister15:19
tomasztrebskino, not yet15:20
rhochmuthi'm assuming you want this for both metrics and logging15:20
witekpython persister is 3x slowlier than java15:20
tomasztrebskidoing this in monasca-common would have potential impact (good one) on every project using that15:20
rhochmuthso, are we using monasca-common for kafka everywhere at this point?15:21
*** yingjun has quit IRC15:21
tomasztrebskiehm...I thought so, actually now that you asked I am not really sure15:21
tomasztrebskilog-api is using that for sure15:21
*** yingjun has joined #openstack-meeting-315:21
rhochmuthjoe was running into crashes with the latest kafka client15:22
rhochmuthnot sure if those have been resovled15:22
rhochmuthbut this would obviousely bypass that15:22
*** slaweq has left #openstack-meeting-315:22
rhochmuthwould you want to update global requirements?15:22
rhochmuthwe might run into problems there15:23
tomasztrebskiwith confluent-kafka ?15:23
rhochmuthcorrect15:23
tomasztrebskithat might be problematic, because it requires compiling one C-library15:23
rhochmuthmy assumption is that they won't want two kafka libraries15:23
tomasztrebskirdkafka15:23
witekwhat are the requirements to get added to global-requirements?15:23
*** m1dev has quit IRC15:23
tomasztrebskiadd change to one infra projet and see how it goes ? :D15:24
*** baoli_ has quit IRC15:24
*** m-greene has joined #openstack-meeting-315:24
rhochmuthusually nice well supported python code which is properly licenses15:24
rhochmuthand doesnt' compete with an existing library15:24
rhochmuthindustry adoption15:24
witekthe second one is not the case here15:24
rhochmuthperformance would be another criteria15:25
*** rbrndt has joined #openstack-meeting-315:25
rhochmuthso, we got ujson in15:25
witekit is also relatively new15:25
*** absubram has joined #openstack-meeting-315:25
rhochmuthwhich compete with json and simplejson15:25
tomasztrebskiboth are based on Apache, but I would not go that far right now, I mean first we should clarify if the API of the confluent-kafka-python meets all the requirements that monasca presents15:25
rhochmuthso, it might be accepted based on the performance analysis15:25
rhochmuthbut i expect it will be questioned15:25
tomasztrebskiperformance on one side, but the capabilities on the other15:25
rhochmuthright15:25
rhochmuthso, i'll let you guys drive that15:26
rhochmuthi wasnt' looking at reviews for a few days15:26
rhochmuthso, little behind15:26
tomasztrebskiok, guess now we will need to discuss that internally and give feedback from your feedback and plan that somehow15:26
rhochmuthsure15:27
rhochmuthshoudl we move on15:27
tomasztrebski+115:27
rhochmuth#topic https://review.openstack.org/#/c/366024/15:27
*** openstack changes topic to "https://review.openstack.org/#/c/366024/ (Meeting topic: monasca)"15:27
rhochmuthmigrate devstack to xenial15:27
shinya_kwbtthere are vagrant problem.15:28
tomasztrebskione of our (mine, Witek) folks tested this recently for both Java&Python15:28
tomasztrebskiit stacks up with workaround15:28
rhochmuthwhat was the work-around?15:28
tomasztrebskishinya_kwbt: problem you have can be solved with starting up machine without provision and than creating one snapshot15:29
*** rajinir has joined #openstack-meeting-315:30
shinya_kwbtI solved with that15:30
shinya_kwbt1. vagrant up --no-provision && vagrant halt 2. open virtualbox gui 3. open target vm settings and change storage controller from SCSI to SATA 4. vagrant up15:30
tomasztrebskiso instead of vagrant destroy -f ; vagrant up for clean install, you would do vagrant sandbox rollback ; vagrant provision15:30
witekI have also tested with bento box, but it exited on smoke tests15:30
tomasztrebskiassuming using vagrant-sahara15:30
shinya_kwbtwitek: me either15:30
shinya_kwbtnot vagrant environment works fine so I think tempest-gate may work15:31
tomasztrebskiI assume so too, looking at other projects that already moved to xenial15:32
tomasztrebski@witek actually created a change that would result in NV gate for ubuntu-xenial15:32
tomasztrebskiwe would see any issues with that prior to merging shinya_kwbt change15:33
tomasztrebskihttps://review.openstack.org/#/c/397789/15:33
*** alexismonville has joined #openstack-meeting-315:34
rhochmuthso, that review looks like is should be merged15:35
rhochmuthas it is experimental15:35
witekyes15:35
witekfor agent, non-voting15:35
rhochmuththen we can see if shinya's merge works15:35
witekthe rest experimental15:35
witekI hope it works this way :)15:35
shinya_kwbtrhochmuth: thanks15:35
rhochmuththen we can see if shinya's review works15:35
rhochmuthand if it does, it can be merged15:35
rhochmuththen can change from experimental15:36
witekcorrect15:36
rhochmuthalthough Vagrant will still be partly broken15:36
rhochmuthwith xenial15:36
rhochmuthafter shinya's change merges if i understand correctly15:37
shinya_kwbtYes virtual box SCSI controller has problem. Trusty image has SATA controller but xenial has SCSI.15:37
rhochmuththose bastards15:37
witekvagrant is still an issue, but I think we can merge it if gate tests pass15:37
tomasztrebskiwell we could try and try to solve that to make vagrant work on trusty still, I have at least one idea for that15:37
tomasztrebskior two15:37
rhochmuth:-)15:37
tomasztrebski;-)15:37
rhochmuththanks tomasz15:38
rhochmuthso, i'm going to put a +1 on your experimental review witek15:38
rhochmuththen we can watch what happens next15:38
tomasztrebskidon't thank me now...not really sure if I will find any time to devote any time to that15:38
witekthank you15:38
rhochmuthwelcome15:39
rhochmuthdone15:39
rhochmuththanks witek and shinya!15:39
rhochmuthadn tomasz and everyone15:39
*** spzala has joined #openstack-meeting-315:39
*** SWDevAngel_ has quit IRC15:40
*** hoppalm has joined #openstack-meeting-315:40
shinya_kwbtthanks tomasz witek15:40
rhochmuth#topic https://review.openstack.org/#/c/384128/15:40
*** openstack changes topic to "https://review.openstack.org/#/c/384128/ (Meeting topic: monasca)"15:40
*** SWDevAngel_ has joined #openstack-meeting-315:40
rhochmuthtomasz, that is you15:41
rhochmuthGranular logging control15:41
tomasztrebskiit just to remind to take a look, already have monasca-api and monasca-log-api working with new logging configuration, so it would just supplement what has been already done in that topic15:41
tomasztrebskiagent and notification components are not that easy to refactor it to work with oslo.log15:42
rhochmuthok, looks fine to me15:42
tomasztrebskinot to mention that it would be like revolution there instead of simple refactor15:42
rhochmuthbut i should look at it a little closer15:42
tomasztrebskinp15:42
rhochmuth#topic https://review.openstack.org/#/c/391576/15:42
*** openstack changes topic to "https://review.openstack.org/#/c/391576/ (Meeting topic: monasca)"15:42
*** hoppalm has quit IRC15:43
tomasztrebskialso me15:43
rhochmuthit is failing15:43
rhochmuthbut, i think it is a good idea15:43
tomasztrebskiyeah and it will, because it requires gate change15:43
tomasztrebskithis is not like zookeeper change I posted sometime ago15:43
*** iyamahat has joined #openstack-meeting-315:44
tomasztrebskizookeeper is builtin inside the devstack15:44
tomasztrebskikafka is a yet another plugin15:44
*** tqtran has joined #openstack-meeting-315:44
tomasztrebskibut if you find it a good idea, I will work on this in my free time15:44
rhochmuththe only issue i have is that we might want to consdier upgradign to the newest kafka15:44
rhochmuth0.10.1 or later15:45
tomasztrebskiwe might go with another gate with would be NV and use newer kafka15:45
tomasztrebskiluckily version of kafka is part of plugin/settings so can be overidden in gate setup15:46
tomasztrebskiplugin also specify such variables AFAIK15:46
rhochmuthwell, in general then i think it is a good idea15:46
rhochmuthwhat other projects are using kafka?15:46
rhochmuthdo you know15:46
*** coolsvap is now known as coolsvap_15:46
tomasztrebskino idea15:47
tomasztrebski:(15:47
rhochmuththe problem is that the kafka releases are incompatible15:47
rhochmuthso, i think  you are approved tomasz to proceed if you want to15:48
*** tqtran has quit IRC15:48
rhochmuthi can't see any problems15:48
rhochmuthseems like we are covered15:48
rhochmuthif we want to upgrade15:48
*** armax has joined #openstack-meeting-315:49
tomasztrebskii will figure sth out ;), at least working on using plugin in monasca and/or new gate15:49
rhochmuthok, thanks15:49
*** zhipeng has quit IRC15:49
rhochmuth#topic https://review.openstack.org/#/c/395246/15:49
*** openstack changes topic to "https://review.openstack.org/#/c/395246/ (Meeting topic: monasca)"15:49
rbakThese two are mine15:49
tomasztrebskiwitek: the same gate should be done also to the log-api devstack jobs15:50
rbakJust trying to get some attention on them15:50
rbakWe're trying to backfill data, but we're blocked by lacking these abilities15:50
*** ociuhandu has joined #openstack-meeting-315:51
rhochmuthso, does anyone have any opinions on those two reviews15:51
*** uxdanielle has quit IRC15:52
*** pratid has joined #openstack-meeting-315:52
tomasztrebskiyeah, just posted one ;d15:52
rhochmuthi thought about the backfill problem15:52
rhochmuthwasn't sure if this should just be a admin feature15:52
rbakIt's not something we would want to expose to customers15:53
rhochmuthwas wondering since it isn't in python, if it shoudl be added15:53
rbakAlthough we could tie it to a brand new role15:53
rhochmuth"backfill" role15:53
rhochmuthsounds a bit combersome15:53
rhochmuthcomplicated15:53
rbaktomasztrebski: I'm not sure I follow your comment on that patch, can you elaborate?15:53
tomasztrebskiAFAIK, we should not go into role mores, I would consider moving to policies...I know that is a lot of work but there is a reason why there's a dedicated oslo library for that15:54
rbakrhochmuth: Yeah, we just went with the cleanest solution for the moment.15:54
*** catherine_d|1 has joined #openstack-meeting-315:54
*** xdreamer has left #openstack-meeting-315:54
rhochmuthyeah, the problem is that java code doesn't support oslo15:54
tomasztrebskiahhh....java ;/15:55
rhochmuthbut getting the python code to implement the rbac like the rest of openstack would be good15:55
rhochmuthbeen on the list forever15:55
*** lpetrut has quit IRC15:55
tomasztrebskiso in case of +1 for policies that would require extra work for java15:55
*** catherine_d|1 has quit IRC15:56
rhochmuthanyway, i thought about this a bit15:56
rhochmuthwhether the right direction15:56
rhochmuthi can't see any problems with what is being proposed in the review15:56
*** catherine_d|1 has joined #openstack-meeting-315:56
rhochmuthand, it sounds like we don't want to do anything with the python code for this case15:56
rhochmuthright?15:56
rbakNot for the moment anyway.15:57
*** donghao has joined #openstack-meeting-315:58
rhochmuthshould we move to #openstack-monasca?15:59
rhochmuthwe are at the end of the hour slot15:59
witekI would prefer to move the rest to next week15:59
tomasztrebskiuh...I won't be able to join, got to go out15:59
tomasztrebskime too16:00
rhochmuthi won't be around next week16:00
tomasztrebskiwhat can be covered in gerrit, let's cover it there16:00
rhochmuthok, see you in two weeks16:00
tomasztrebskibye16:00
rhochmuth#endmeeting16:00
shinya_kwbtthanks bye16:00
witekbye16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Nov 16 16:00:37 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
*** coolsvap_ is now known as coolsvap16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-11-16-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-11-16-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-11-16-15.00.log.html16:00
*** koji has quit IRC16:00
*** hosanai has quit IRC16:00
*** arturbasiak has quit IRC16:00
*** shamail has joined #openstack-meeting-316:00
eglute#startmeeting defcore16:01
openstackMeeting started Wed Nov 16 16:01:00 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** rbrndt has left #openstack-meeting-316:01
*** yingjun has left #openstack-meeting-316:01
*** openstack changes topic to " (Meeting topic: defcore)"16:01
markvoelkero/16:01
openstackThe meeting name has been set to 'defcore'16:01
catherine_d|1o/16:01
shamailo/16:01
eglute#chair markvoelker16:01
openstackCurrent chairs: eglute markvoelker16:01
hogepodgeo/ (from SuperComputing 16)16:01
eglute#chair hogepodge16:01
openstackCurrent chairs: eglute hogepodge markvoelker16:01
*** uxdanielle has joined #openstack-meeting-316:01
egluteHello Everyone!16:01
eglute#topic agenda16:01
*** openstack changes topic to "agenda (Meeting topic: defcore)"16:01
egluteplease review the agenda for today: #link https://etherpad.openstack.org/p/DefCoreRoble.316:01
*** pratid has quit IRC16:02
eglute#topic meeting time16:02
*** openstack changes topic to "meeting time (Meeting topic: defcore)"16:02
GheRiveroo/16:03
eglutewith all the travel, conferences and time changes, we missed a couple last meetings. With the time change, does this time still work for everyone?16:03
markvoelkerThis timeslot continues to be fine for me.16:03
egluteworks for me as well :)16:03
markvoelkerAnd FWIW, I plan on being available next week--leaving for Thanksgiving almost right after this meeting though. =)16:03
hogepodgeworks for me16:03
shamail+116:03
gemao/16:04
catherine_d|1I would prefer it to be one hour later ... but will try to attend at the current time16:04
hogepodgeSame for me on American Thanksgiving holiday, despite my travel unavailability over the last month. I need a holiday.16:04
gemabeing thanksgiving next week maybe we should cancel and discuss the time for the week after16:04
eglutecatherine_d|1 noted about one hour later... lets see what others say16:05
*** tomasztrebski has quit IRC16:05
eglutegema good suggestion16:05
catherine_d|1eglute: thank you16:05
gemaone hour later works for me also probably better16:06
eglutei can be around next week, but seems like some will be out.16:06
eglutegema noted!16:06
markvoelkerAn hour later would actually be challenging for me...16:06
*** atuvenie has quit IRC16:06
eglute#action discuss meeting time change after next week16:06
eglutemarkvoelker we need you at this meeting, so lets see how things look in a couple weeks16:07
hogepodgeI prefer to keep the UTC time, since changing it twice a year is a pain.16:07
eglutehogepodge agreed..16:07
hogepodgeMost projects don't move their meeting time from what I understand.16:07
*** yamahata has joined #openstack-meeting-316:07
dmelladoo/16:07
*** kgarloff has joined #openstack-meeting-316:08
egluteok... so just to get consensus on next week16:08
eglute+1 if we should cancel next week16:08
*** witek has left #openstack-meeting-316:08
gema+116:08
shamail+116:08
hogepodge+116:08
catherine_d|1+116:08
dmellado+116:08
markvoelker+0 (fine either way)16:08
kgarloff+016:09
*** gouthamr has joined #openstack-meeting-316:09
eglute+0 for me as well, but canceling seems to win16:09
luzCo/16:09
eglute#agreed no meeting next week16:09
eglute#topic Flag volume_from_snapshot test from 2016.0816:10
*** openstack changes topic to "Flag volume_from_snapshot test from 2016.08 (Meeting topic: defcore)"16:10
eglute#link https://review.openstack.org/#/c/385216/16:10
markvoelkerThis one is abandoned16:10
egluteoh, i am too slow!16:11
eglutei guess we are good then16:11
eglute#topic 2017.01 Guideline16:11
*** openstack changes topic to "2017.01 Guideline (Meeting topic: defcore)"16:11
egluteshamail do you have an update on cinder?16:11
shamailHi eglute, I do not.  I had to leave the summit early and didn’t check the etherpad yet.  I will work on this update later this week and early next week (if needed).16:12
eglutethanks shamail16:12
egluteMoving on to swift16:13
shamailyou’re welcome16:13
egluteI started breaking out the patch i had originally submitted16:13
eglutenew patch for new capabilities: #link https://review.openstack.org/#/c/398428/16:13
eglutei am not sure how to handle some of the things, like consolidating existing capabilites16:14
egluteone of them is that16:14
*** millerthomasj has quit IRC16:14
eglutealso, one renamed capability16:14
egluteand one brand new one16:15
eglutei scored others as well, as suggested by ptl16:15
egluteplease review my scoring :)16:15
*** matjazp has quit IRC16:15
eglutei still have to submit a patch with new tests that were suggested, i will work on that today16:16
* markvoelker plans to work on that this week now that post-summit stuff has calmed down16:16
*** armax has quit IRC16:16
eglutethanks markvoelker... catching up after this summit has been really hard16:16
markvoelkeryup16:17
egluteany comments on swift? or ideas how to handle renames for capabilities? or suggestions on adding new tests to capabilities?16:17
*** rtheis_ is now known as rtheis16:17
markvoelkereglute: none off the cuff, but I may once I get a chance to look at it more (probably tomorrow)16:18
eglutethanks markvoelker!16:18
egluteif no comments on swift, can move to nova16:19
eglute#link https://review.openstack.org/#/c/385781/16:19
eglutethanks luzC for reviewing it16:19
hogepodgethis has been the busiest I've even been after a summit, and I've done very little defcore work outside of logo and test admin16:19
*** caboucha has joined #openstack-meeting-316:19
*** matjazp has joined #openstack-meeting-316:20
hogepodgeMT will be catchup days for me on 2017.01 reviews16:20
eglutehogepodge i understand! I been slow to catch up as well16:20
eglutethere are some good comments on the nova patch16:21
eglutethanks shamail for submitting it16:21
markvoelkerOne thing I noted in that review was the comment about AZ's, which I think has some merit16:22
*** donghao has quit IRC16:22
markvoelkerI need to go look at those tests a bit, but seems like lisitng AZ's is sound addition.16:22
egluteagree... also new capabilities need to be as advisory first16:22
shamailI can remove list-api-versions since it is already added.  I scored it again because I was unfamiliar with the process.16:22
eglutealso, i think the compute-flavors-list was already there at some point. i think i said i would look into it and never did16:23
*** armax has joined #openstack-meeting-316:23
shamailThe reason I added them was because they have been around for multiple releases (I assumed advisory for newly added functionality, not capabilities guidelines)16:23
markvoelkershamail: I think it's fine...sometimes scores change over time, so it's perfectly fine to update them16:23
shamailbut happy to change that as well16:23
shamailDo all new guidelines go through advisory first? (asking for my own benefit)16:24
egluteyes16:24
shamailOkay :)16:24
shamailWill update16:24
eglutewell, they should.16:24
*** numans has quit IRC16:25
egluteexcept in swift case, i have one where it is a rename or something like that. still a grey area on that one16:25
egluteuntil we decide what to do :)16:25
eglute#action eglute research what happened to compute-flavors-list16:26
egluteeveryone, please review nova patch16:26
markvoelkerIs it grey?  We're explicitly allowed to change groupings.  http://git.openstack.org/cgit/openstack/defcore/tree/doc/source/process/2016A.rst#n7116:26
egluteoh, that helps! thanks markvoelker!16:26
egluteany other comments on nova?16:27
egluteif not, moving on to heat16:28
eglutecatherine_d|1 gema and I met with the Heat team in Barcelona16:28
egluteHeat is considering moving Gabbi tests: https://review.openstack.org/#/c/348076/16:28
egluteProblem: Tempest currently does not support Gabbi, so additional delay.16:29
*** rhagarty_ has joined #openstack-meeting-316:29
egluteAll tests will be new, so would have to go through the "stable test" period. Suggestion: add them as advisory before they are considered "stable" for 2 cycles, and potentially keep them for advisory 2-3 cycles.16:29
eglutethese were my notes from that meeting16:29
*** mickeys has joined #openstack-meeting-316:29
eglutecatherine_d|1 gema please add or correct if i missed anything16:29
*** krtaylor has quit IRC16:29
eglutebut basically, heat doesnt look good16:30
eglutefor adding them soon16:30
catherine_d|1eglute: yea looks like that is the case16:30
catherine_d|1Just one note that with Gabbi .. these would be pure API tests ...16:31
eglutei think that would be ok16:31
markvoelkerAnd currently still planned for in-heat-tree vs in-tempest-tree, right?16:31
eglutegabbi would help with the in tempest tree part16:31
catherine_d|1it will be in-heat tree with tempest plugin interface first16:32
markvoelkerOk, so as things currently stand with the TC they'd still be hard to consider anyway...16:32
catherine_d|1Once test are in Tempest plug-in interface moving to Tempest would be easy16:33
hogepodgethe idea was that tests would move only when required16:33
eglutei think once they have gabbi tests, we can consider them when they are still in plugin, with the understanding that they would move the tests16:33
hogepodgeper conversation with dhellmann at summit16:34
catherine_d|1hogepodge: exactly .. that is why all new tests development will be in-tree with plug-in implementation first16:34
*** mickeys has quit IRC16:34
hogepodgeso start with plug in and move tests if added to defcore16:34
markvoelkersounds good16:34
catherine_d|1hogepodge: yup16:34
egluteany other comments on heat?16:35
catherine_d|1I am good16:35
eglutethanks catherine_d|1!16:35
eglutemoving on to keystone16:35
eglutehogepodge, did you have a chance to look at it?16:36
hogepodgeeglute: no, I can give it attention starting Monday16:36
eglutethanks hogepodge!16:36
markvoelkerI've got a couple of candidates from the PTL...it's late, but I can probably push a scoring patch this week if folks can review it16:36
hogepodgeyes please.16:36
eglutemarkvoelker that would be good!16:36
markvoelkerIt will be fairly short, so not hard to review. =)16:37
eglute:)16:37
egluteNeutron: patch was merged, thanks markvoelker!16:37
markvoelkerBasically list user's groups, list user's projects, change user's password, and show user I think.16:37
eglutesounds good!16:37
egluteGlance: markvoelker did you have a chance to look at it?16:38
markvoelkerYeah, I talked this over with some Glance folks.  I don't think we're going to have a lot of additions here, but a little housekeeping might be in order16:38
egluteworks for me!16:38
markvoelkerE.g. we have a few places where we say something like "v1 API is SUPPORTED but not the CURRENT version"...but v1 is now DEPRECATED16:38
markvoelkerThat should be a pretty trivial patch, which I can probably also push this week16:39
egluteoh yeah, def. need to do something about that16:39
eglutethanks markvoelker16:39
egluteany other comments/updates on 2017.01 guideline?16:40
eglute#topic Name change16:40
*** openstack changes topic to "Name change (Meeting topic: defcore)"16:41
eglutemarkvoelker shamail hogepodge any updates?16:41
hogepodgeI need to check with fungi about the mailing list.16:41
hogepodgeI ran it by him at the summit, and need to follow up.16:41
shamailNone, but I think the note in the etherpad is worth mentioning16:42
fungiyep, i promised to show you what file to propose a change to16:42
*** paul-carlton2 has quit IRC16:42
shamailPlease switch to the #openstack-interop channel if you haven’t already done so16:42
eglutethanks shamail16:42
shamailhogepodge: can you also ask about the Wiki?16:42
eglutethanks hogepodge and fungi16:42
hogepodgeThe procedure there would be to set up new mailing list, send an announcement to everyone on current list to move, then shut down old list by removing all membership and leaving the archive intact.16:42
shamailThere is a copy option but I didn’t want to try it without asking16:42
*** kzaitsev_mb has quit IRC16:42
markvoelkerWe had discussed a goal to get all the wheels in motion on the name change by the end of the year IIRC.  So I plan on taking this up a bit more once I get 2017.01 cleared off my plate.16:43
markvoelkerI know I've got a few AI's outstanding, and have patchwork started on a couple of them16:43
shamailThe meeting doesn’t really need to change (besides the name)… I can submit that patch soon too16:43
*** krtaylor has joined #openstack-meeting-316:43
hogepodgeDecember seems like a good month to finish it off, and aligns with the schedule I had in my mind.16:43
eglutehogepodge can the subscribers be copied to the new mailing list?16:43
shamailThe gerrit and git repo changes are probably the ones you want to handle markvoelker16:44
markvoelkershamail: yep, on my list16:44
hogepodgeeglute: I don't believe so. The general policy for mailings is opt-in16:44
shamailNot that I am aware of eglute (we are going through the same task in Product WG)16:44
shamailAs admins, you can seee the current subscribers but cant subscribe them16:44
fungiyeah, it's a question of whether you can vs whether you should16:44
shamailmy recommendation would be to get the list of current subscribers and send them a BCC’d note informing them about the change and a link to sign up16:45
shamaila one time notification/heads up isn’t overkill16:45
hogepodgeshamail: The change info will go out to all subscribers, so everyone will be notified.16:45
shamailgood point16:45
fungithere is a mass subscribe page you have access to as list admins but it can be a bit surprising for people to suddenly find themselves subscribed to a new mailing list they dodn't request16:45
hogepodgeIf they miss it because of mail filters, then they may not want to subscribe to the new one anyway16:45
shamailfungi: +1, I think opt-in is best16:46
markvoelkeryeah, I don't think subscribing to an ML is too much action to request of anyone that actually wants to be involved. =)16:46
*** bpokorny has joined #openstack-meeting-316:46
*** reedip_ has quit IRC16:47
egluteok, so opt-in it is for the new mailing list16:47
*** kgarloff has quit IRC16:47
shamailfungi: Will the action > move option in wikis help us migrate our wiki to a new name?16:47
*** kgarloff has joined #openstack-meeting-316:47
shamailor is it better to just do it by hand?16:47
shamailI wasn’t sure what the impact would be to the existing page if that option is used.16:48
fungishamail: moving wiki pages works fine16:48
shamailThanks16:48
fungiit will optionally (and by default) leave a redirect from the old name for you too16:48
shamailThat’s perfect.16:48
shamailI will go ahead and take that one then16:48
egluteany other comments on the rename?16:49
eglute#action shamail to move wikis16:49
fungiper recent additional security measures we put in place, you have to be a "verified" (autopatrolled) account to be able to move wiki pages now, but pretty much all of you are already16:49
eglutethanks fungi!16:50
shamailThank you fungi and hogepodge!  Great information.16:50
eglute#topic Documenting how projects can become part of Guidelines16:50
*** openstack changes topic to "Documenting how projects can become part of Guidelines (Meeting topic: defcore)"16:51
eglutemarkvoelker updates on this?16:51
egluteah, no updates16:51
* eglute read etherpad16:51
markvoelkerOn my backlog.  I'll probably not get to this until after Thanksgiving, realistically16:51
eglutethanks markvoelker!16:51
egluteno rush on that one16:51
eglute#topic Upcoming events: PTG16:52
*** openstack changes topic to "Upcoming events: PTG (Meeting topic: defcore)"16:52
eglutehogepodge, any updates on the time slot?16:52
hogepodgeeglute: Uhm, it's not great news16:52
egluteoh?16:52
*** absubram has quit IRC16:53
hogepodgethe ptg is reserved for TC approved projects. We could possible take advantage of time set aside for refstack, but dedicated space over the course of several days will not be made available to us16:53
gemahogepodge: shall we then continue to have our own separate midcycles?16:53
catherine_d|1RefStack can request for room .. but seems like not many RefStack team member will be able to attend PTG ... I wonder whether we can combine the RefStack and DefCore meeting at PTG16:53
eglutei like the catherine_d|1 suggestion for now, but we need to resolve the "not TC project" part16:54
hogepodgecatherine_d|1: that was proposed as a solution, but keep in mind that this is a lot of shared space that will be allocated according to project size and need16:54
egluteopinions?16:55
markvoelkerSounds to me like a separate midcycle might actually work better if we don't think refstack can get much time/space16:55
hogepodgeI'm not thrilled about it, but it's the TCs purview16:55
markvoelkerhogepodge: ++16:55
eglutehow do people feel about dedicated midcycle?16:55
hogepodgeIt we want to push it, we could raise it formally at a TC meeting.16:56
egluteI am sure Rackspace would be happy to host it in San Antonio :)16:56
* markvoelker wonders if anyone would be interested in hosting us in ATL, say, the week of the PTG...16:56
hogepodgeeglute: I was looking forward to the PTG promise of less travel, but the meetings have been important so I'll continue to support them16:56
gemamarkvoelker: that would be rad x)16:56
egluteI think because of the work we do, we should fall under crossprojects somwhere16:57
hogepodgemarkvoelker: heh, that sounds like a good idea16:57
gemacatherine_d|1: does IBM have offices there?16:57
gemaor rackspace :D16:57
eglutei like the suggestion of asking TC for space at PTG16:57
egluteI can find out out about our office in Atlanta, not sure how big/small it is16:58
gema:)16:58
catherine_d|1I don't recall that we have development site .... I doubt it but can check16:58
eglutewe are almost out of time-- hogepodge could ask TC for space at PTG?16:59
hogepodgeto be clear, we're invited to the PTG, we just can't get a dedicated room or extended resources. Meeting for cross project work is encouraged16:59
shamailI can’t make it, kids are off from school that whole week.16:59
eglutelets ask for dedicated room if most of us would be able to make it16:59
hogepodgeeglute: sure, I can put it on the agenda16:59
eglutethank you hogepodge16:59
shamailWill Interop WG still have a midcycle or is PTG the midcycle for this team16:59
shamailnm17:00
shamailcatching up on the previous messages17:00
egluteand we are out of time... lets move to openstack-interop channel17:00
*** absubram has joined #openstack-meeting-317:00
eglutewill discuss last topic next meeting17:01
eglutethansk everyone17:01
eglute#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
openstackMeeting ended Wed Nov 16 17:01:02 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-16-16.01.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-16-16.01.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-16-16.01.log.html17:01
*** shamail has quit IRC17:01
*** tellesnobrega has quit IRC17:02
*** mgould has joined #openstack-meeting-317:02
*** Rockyg has joined #openstack-meeting-317:04
*** tellesnobrega has joined #openstack-meeting-317:05
*** mgould has left #openstack-meeting-317:08
*** Rockyg has quit IRC17:10
*** andreas_s has quit IRC17:10
*** jobrs has quit IRC17:11
*** rtheis_ has joined #openstack-meeting-317:14
*** ociuhandu has quit IRC17:14
*** rtheis has quit IRC17:15
*** stevejims has left #openstack-meeting-317:16
*** bpokorny has quit IRC17:23
*** matrohon has quit IRC17:23
*** Swami has joined #openstack-meeting-317:29
*** bpokorny has joined #openstack-meeting-317:29
*** baoli has joined #openstack-meeting-317:30
*** absubram has quit IRC17:37
*** iyamahat has quit IRC17:45
*** david-lyle has quit IRC17:48
*** david-lyle has joined #openstack-meeting-317:48
*** catherine_d|1 has left #openstack-meeting-317:51
*** uxdanielle has quit IRC17:52
*** claudiub has quit IRC17:52
*** julim has quit IRC17:54
*** iyamahat has joined #openstack-meeting-317:56
*** ralonsoh has quit IRC17:58
*** yamahata has quit IRC18:01
*** iyamahat has quit IRC18:02
*** bpokorny has quit IRC18:05
*** pkoniszewski has quit IRC18:07
*** egallen has quit IRC18:09
*** pkoniszewski has joined #openstack-meeting-318:10
*** m-greene has quit IRC18:12
*** mickeys has joined #openstack-meeting-318:13
*** tqtran has joined #openstack-meeting-318:13
*** absubram has joined #openstack-meeting-318:14
*** harlowja has joined #openstack-meeting-318:14
*** mickeys_ has joined #openstack-meeting-318:15
*** mickeys has quit IRC18:15
*** bpokorny has joined #openstack-meeting-318:15
*** xavierr has left #openstack-meeting-318:16
*** tqtran has quit IRC18:18
*** sambetts is now known as sambetts|afk18:18
*** mickeys_ has quit IRC18:19
*** iyamahat has joined #openstack-meeting-318:20
*** uxdanielle has joined #openstack-meeting-318:27
*** julim has joined #openstack-meeting-318:37
*** yamahata has joined #openstack-meeting-318:40
*** m-greene has joined #openstack-meeting-318:40
*** julim has quit IRC18:50
*** julim has joined #openstack-meeting-318:55
*** matjazp has quit IRC18:55
*** julim has quit IRC18:55
*** kzaitsev_mb has joined #openstack-meeting-318:56
*** julim has joined #openstack-meeting-318:57
*** gouthamr has quit IRC18:57
*** gouthamr has joined #openstack-meeting-318:59
*** galstrom_zzz is now known as galstrom19:04
*** coolsvap has quit IRC19:07
*** olaph has joined #openstack-meeting-319:08
*** tqtran has joined #openstack-meeting-319:14
*** pvaneck has joined #openstack-meeting-319:14
*** spotz is now known as spotz_zzz19:15
*** haleyb_ has quit IRC19:20
*** olaph has left #openstack-meeting-319:22
*** flwang1 has joined #openstack-meeting-319:22
*** matrohon has joined #openstack-meeting-319:26
*** caboucha has quit IRC19:28
*** lpetrut has joined #openstack-meeting-319:29
*** absubram has quit IRC19:30
*** kzaitsev_mb has quit IRC19:32
*** flwang1 has quit IRC19:33
*** logan- has joined #openstack-meeting-319:33
*** betherly_ has joined #openstack-meeting-319:35
*** kzaitsev_mb has joined #openstack-meeting-319:35
*** tellesnobrega has quit IRC19:36
*** lpetrut has quit IRC19:36
*** tellesnobrega has joined #openstack-meeting-319:38
*** gugl has joined #openstack-meeting-319:39
*** kzaitsev_mb has quit IRC19:40
*** tongli has quit IRC19:40
*** absubram has joined #openstack-meeting-319:42
*** makowals_ has joined #openstack-meeting-319:45
*** rdopiera has joined #openstack-meeting-319:48
*** haleyb_ has joined #openstack-meeting-319:49
*** galstrom is now known as galstrom_zzz19:49
*** pcaruana has quit IRC19:51
*** uxdanielle has quit IRC19:52
*** ducttape_ has joined #openstack-meeting-319:53
*** r1chardj0n3s has joined #openstack-meeting-319:53
*** haleyb_ has quit IRC19:53
*** diablo_rojo_phon has joined #openstack-meeting-319:56
*** ErnestMillan has joined #openstack-meeting-319:56
*** robcresswell has joined #openstack-meeting-319:56
* ducttape_ grabs a seat at the front of the classroom19:57
r1chardj0n3suhoh, are you going to cause trouble young ducttape_?19:58
ducttape_does a bear utilize the woods as a restroom ?19:58
ducttape_;)19:58
r1chardj0n3sjust don't make me find the Time Out cards :-P19:59
*** hurgleburgler has joined #openstack-meeting-319:59
r1chardj0n3s#startmeeting horizon20:00
openstackMeeting started Wed Nov 16 20:00:10 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
openstackThe meeting name has been set to 'horizon'20:00
hurgleburgler(◠‿◠✿)ノ20:00
r1chardj0n3so/20:00
rdopierao/20:00
robcresswello/20:00
david-lyleo/20:00
*** clu_ has joined #openstack-meeting-320:00
ducttape_o/20:00
tqtran[=_=]/20:00
rhagarty_o/20:00
clu_o/20:00
*** tonytan4ever has quit IRC20:00
rdopiera.oO( was tqtran replaced by a bot? )20:00
r1chardj0n3sheh20:01
*** tsufiev has joined #openstack-meeting-320:01
*** tonytan4ever has joined #openstack-meeting-320:01
tqtranthats my face each morning, it gets rounder as the day progresses20:01
robcresswellwoah so many people20:01
* r1chardj0n3s wasn't going to jinx it20:01
tsufievwho's there :)?20:01
robcresswell\o/20:02
r1chardj0n3sI'll start off with the usual stuff20:02
rdopieraknock knock20:02
r1chardj0n3s#topic Priority patches for review20:02
*** openstack changes topic to "Priority patches for review (Meeting topic: horizon)"20:02
hurgleburglerhehe20:02
hurgleburgleris a full party today!20:02
r1chardj0n3s#link https://review.openstack.org/#/q/starredby:r1chardj0n3s%20AND%20status:open lists the patches we need to get reviewed ASAP20:02
hurgleburgler♪└|∵|┐♪└|∵|┘♪┌|∵|┘♪ ♪└|∵┌|└| ∵ |┘|┐∵|┘20:02
r1chardj0n3sthough since I'll be tagging O-1 tomorrow (or maybe Saturday if we're optimistic about any of those patches) they probably won't be making it in20:02
rdopieraI have a question about the priority reviews -- should we also reviews the ones that are marked as work in progress?20:03
r1chardj0n3sI've got a busy Saturday morning though.20:03
* tsufiev on his way to address the latest comments in profiler patch20:03
robcresswell<< guilty of WIP20:03
robcresswellThat tox patch keeps growing. Because we thought it would be fun to put all our translation infra for babel inside run_tests :(20:03
r1chardj0n3srobcresswell: I think maybe the tox one might not make it this week, but I'm also not sure that's a huge problem20:03
robcresswellNo, its progressing fine, its just turned out to be a bigger job than I thought.20:04
robcresswellstory of openstack I suppose.20:04
r1chardj0n3ssince it doesn't really have any knock-on effects to others like frameworks would20:04
r1chardj0n3sbut it would be super nice for everyone to stop using run_tests as soon as possible this release20:04
r1chardj0n3sso, you know, get on with it20:04
r1chardj0n3s:-)20:04
rdopierafortunately I didn't setup ci for 11 yet20:04
* tsufiev expects a lot of complaints once it's finally done20:05
ducttape_r1chardj0n3s / robcresswell - should / could we add a quick patch to bark at people and say "use this instead please" ?20:05
ducttape_for tox that is20:05
robcresswellAlready done that. If you use run_tests it has a big warning for every command20:05
robcresswellSomething about it being removed.20:06
robcresswellClearly it was very noticeable.20:06
r1chardj0n3syeah. maybe it could USE SOME BOLD ? :-)20:06
ducttape_how does the blink tag work in the cli ?20:06
ducttape_;)20:06
r1chardj0n3sOnce O-1 is tagged I'll start loading the various next priority patches into the starred list. If you have favourites you'd like to encourage me to list there, please let me know.20:06
tsufievBIG BOLD RED BLINK :D20:07
hurgleburgler+220:07
r1chardj0n3sducttape_: ANSI code 5 or 620:07
r1chardj0n3syou're welcome20:07
* ducttape_ did not expect this wealth of info20:08
r1chardj0n3sok, moving on20:08
r1chardj0n3s#topic Priority bugs20:08
*** openstack changes topic to "Priority bugs (Meeting topic: horizon)"20:08
david-lylerobcresswell: https://github.com/openstack-infra/project-config/blob/ad92dd20289c1861c2d0d68eeebd21fa1629a597/jenkins/jobs/horizon.yaml#L79 BTW20:08
r1chardj0n3sI only have one priority bug listed at the moment20:08
r1chardj0n3shttps://bugs.launchpad.net/horizon/+bug/162474320:09
openstackLaunchpad bug 1624743 in OpenStack Dashboard (Horizon) "Project image table: admin user sees images which are not shared with me" [High,In progress] - Assigned to Brad Pokorny (bpokorny)20:09
r1chardj0n3sIt'd be super nice if someone had some spare time they could look into that one.20:10
ediardoo/20:10
r1chardj0n3s#topic Nova changing simple tenant usage API20:11
*** openstack changes topic to "Nova changing simple tenant usage API (Meeting topic: horizon)"20:11
tsufievso the patch is https://review.openstack.org/#/c/375170/ r1chardj0n3s?20:11
r1chardj0n3s#link https://review.openstack.org/#/c/386771/ is a spec for changing the API20:11
tsufievperhaps add it to priority patches?20:11
r1chardj0n3stsufiev: thanks, I had missed that patch! I'll star it and review it today20:11
tsufiev:)20:12
bpokornyLet me know if you guys have any questions on the patch.20:12
r1chardj0n3sSo the nova folks want to fix the horrible performance of the os-simple-tenant-usage API call, which has been an issue for us in the past.20:12
bpokornyI'm not confident it's been done in the most efficient way, but it's at least a bandaid for the problem :/20:13
r1chardj0n3sthanks bpokorny20:13
*** egallen has joined #openstack-meeting-320:13
bpokornynp20:13
robcresswellstarred it too20:14
ducttape_would be good to improve that, but we would likely need some graceful fall back option too (once it is available)20:14
r1chardj0n3syep20:15
r1chardj0n3srobcresswell: could you please update us on where our xstatic packages are?20:16
robcresswell\o/ Sure. So, we've updated and released several packages now, I've got a patch to the Horizon relnotes that lists them20:16
robcresswellhttps://review.openstack.org/#/c/39830220:17
robcresswellWe're working on ui-bootstrap, d3 4.x, jquery 3.x... they all have breaking changes20:17
rdopierar1chardj0n3s: betherly couldn't come today, but she's working on the pagination patch20:17
robcresswellBut overall, making good progress.20:18
r1chardj0n3swe're still waiting on the patch to limit Mitaka's use of bootstrap so it doesn't break20:18
r1chardj0n3shttps://review.openstack.org/#/c/396447/20:18
*** bpokorny has quit IRC20:18
r1chardj0n3sI'll nudge the requirements folks about that again today20:18
r1chardj0n3sAnd of course all the poor plugins will need to be updated too20:19
robcresswellsounds good20:19
rdopiera#link https://blueprints.launchpad.net/horizon/+spec/simple-tenant-usage-pagination20:19
rdopierawe have a blueprint for it too20:19
r1chardj0n3srdopiera: thanks!20:20
*** bpokorny has joined #openstack-meeting-320:21
r1chardj0n3srobcresswell: so should I also put in requirements limits for Mitaka for d3 and jquery?20:22
*** egallen has left #openstack-meeting-320:22
*** egallen has quit IRC20:22
robcresswellr1chardj0n3s: Yes, I suppose so20:23
r1chardj0n3sMaybe I can get that shoe-horned into the current patch that's not yet merged, though it'd help to know the versions of d3 and jqeury that compatibility was broken in20:23
r1chardj0n3sI'll take that on today20:24
r1chardj0n3sok, moving on20:24
r1chardj0n3s#topic Cookiecutter template for an OpenStack Dashboard UI plugin project20:24
*** openstack changes topic to "Cookiecutter template for an OpenStack Dashboard UI plugin project (Meeting topic: horizon)"20:24
r1chardj0n3s#link https://blueprints.launchpad.net/horizon/+spec/ui-cookiecutter20:24
r1chardj0n3stqtran, I think you are championing this one?20:24
tqtranso shuu isnt here probably20:24
r1chardj0n3syeah20:24
* ducttape_ ❤ cookies20:25
*** ErnestMillan has quit IRC20:25
tqtranhes created a cookie cutter for horizon plugins some time ago20:25
tqtrani think we can potentially reuse this for our own startdash cmd (which doesnt really work)20:25
tqtranwe have one for python but none for angular panels20:25
r1chardj0n3sooh, I like removing code20:25
*** ErnestMillan has joined #openstack-meeting-320:26
david-lylethe command works, just doesn't stub out angular20:26
tqtranso i think we can potentially reuse this for startdash and make it an official horizon repo20:26
tqtranit works, but i think cindy and i found a few bug with it20:26
tqtranthis was some time ago, so i cant be sure now20:26
*** rtheis_ has quit IRC20:26
david-lyleit doesn't get much love20:26
tqtranright, there were recent changes that did not get incorporated20:27
tqtrananyway, point is, this cookie cutter should be an official horizon repo that we support20:27
tqtranand the side benefit is that we can also use it in our own start dash20:27
david-lyleraise your hand if you know startdash and startpanel exist o/20:27
robcresswellSo... the only downside is more code to support, right?20:27
robcresswello/20:27
robcresswellI mean, if we already ignore start*, do we want to add more?20:28
tqtranright, the downside is we (horizon drivers) are now in charge of maintaining that repo20:28
tqtraninstead of shuu20:28
tqtranyes i think we do since new projects can use it to jump start their own project20:28
tqtranit will make life a bit easier20:28
tqtranor we can just point people to shuu's repo, but down side is that if we make changes in the future, shuu's repo is going to be out of touch20:29
tqtranso whats the verdict? should we vote?20:30
ducttape_if shuu's repo is not getting love, I'd say move it into someplace that will look after it, and keep it running20:30
*** flwang1 has joined #openstack-meeting-320:30
r1chardj0n3sI personally need to think about it some before making a decision.20:30
tqtranok, we can revisit after everyone mulls over it20:31
robcresswellMy feeling is that we dont even maintain the existing ones, who's going to maintain the new one?20:31
ducttape_even if it is not working 100% of the time, at least try to use common locations / tooling / etc20:31
robcresswellIts a cool idea, no doubt20:31
*** spotz_zzz is now known as spotz20:31
robcresswellI just dont want to be the one debugging it on IRC with someone in 3 months time.20:31
robcresswell:)20:31
david-lylemy point would be we had startdash and startpanel and they didn't get love and that's in the horizon tree, another repo is going to languish unless it's actively used20:31
ducttape_can this tool be invoked from ./run_tests.sh ?     ;)20:32
robcresswellwait are you saying bring it into Horizon, david-lyle, so it gets more attention?20:32
hurgleburglerlol20:32
david-lylebut it's a good idea and useful tool for sure20:32
david-lylerobcresswell: I'm not sure, TBH20:32
tqtranbut whats the alternative? we are pushing everyone toward plugins, isnt it part of our responsibility to make it easier for them?20:32
david-lyleI just am suspicious how up-to-date it will remain in our care20:33
robcresswelltqtran: Yes, but a broken tool isnt easier for anyone :)20:33
tqtranright now, you have to manually recreate those files, its a bit of a pain20:33
david-lyleis it something we should do? absolutely. Is it something we will do effectively, not sure20:33
tqtranhahaha20:33
r1chardj0n3sSo could we instread update start* in Horizon to be correct?20:34
ducttape_bringing the tool back in, and then deciding to remove it (if it gets no love) - this is an option too20:34
robcresswelldavid-lyle: +120:34
robcresswellducttape_: Have you ever tried taking a feature away from horizon operators before? :)20:34
ducttape_no way, those guys are jerks20:34
robcresswelllol20:34
david-lyleLOL20:34
tqtranr1chardj0n3s: even if we update start dash, we still dont have one for angular20:34
r1chardj0n3s(fwiw I'm not sure we can embed ui-cookiecutter in the Horizon repos and have it still work with the cookiecutter tool)20:35
tqtranso the cookie cutter will still need to come in at some point20:35
david-lyleI guess our poor oversight is better than a complete orphan20:35
tqtrani think so too. some oversight is better than throwing people out in the cold20:36
*** rtheis has joined #openstack-meeting-320:36
ducttape_less bad is the phrase david-lyle20:36
r1chardj0n3s(oh, no, my concern about pulling it in is incorrect)20:36
robcresswellWell, propose a patch20:37
tqtranwe're not the only project to use cookie cutter, tempest is also doing the same thing20:37
robcresswellWe'll see how it goes20:37
r1chardj0n3sso, we have three options, I think? 1) Ignore it and "fix" start* in Horizon, 2) Add ui-cookiecutter as an openstack project under the Horizon tree or 3) pull ui-cookiecutter into Horizon to replace start*20:37
tqtranits just a documentation patch that says, heres is the official horizon-plugin-cookie-cutter, and heres how to use it20:38
r1chardj0n3sBoth 2 and 3 mean shuu can't actively maintain the project any longer without becoming a Horizon core, correct?20:38
robcresswellr1chardj0n3s: You can just give it its own core team that inherits from horizon-core too20:38
*** gugl has quit IRC20:38
r1chardj0n3srobcresswell: ok, good20:39
ducttape_would the horizon cores not just implicitly shuu for many of these patches ?20:39
ducttape_trust ^20:39
david-lyleseparate core works20:39
david-lylelooks the same to everyone otherwise20:40
tqtranhonestly, theres not much code in there. shouldnt be too hard to maintain it. we can just fork over shuu's work and take over20:40
robcresswellYeah, manila already do that, they have their own core team but horizon are cores in it too. I think searchlight ui does it too.20:40
tqtranwe dont have to make him a core to maintain that project20:40
david-lylejust if he wanted20:40
tqtranright, if he wanted20:40
*** m-greene_ has joined #openstack-meeting-320:40
r1chardj0n3syep, having shuu (and potentially others, along with Horizon cores) be core of the project ameliorates the main concern about it being kept up to date I think.20:40
david-lyleif he's dumping and running, yes, there's no pont20:40
*** m-greene has quit IRC20:41
*** m-greene_ is now known as m-greene20:41
david-lyle*point20:41
tqtranim sure he will be happy to maintain it20:41
r1chardj0n3sI don't see any evidence that this is a dump-and-run20:41
*** MarkBaker has quit IRC20:42
r1chardj0n3sSo, the BP also proposes that startdash use ui-cookiecutter instead of the current code.20:43
david-lylewasn't making an accusation, just didn't know the full story20:43
r1chardj0n3sThat would presumably mean Horizon pulling in the cookiecutter tool and invoking it.20:43
r1chardj0n3sAnd removing the existing startdash/startpanel.20:44
*** gugl has joined #openstack-meeting-320:44
tqtrani think that requires a bit more investigation. i have to look into how we can actually hook it up.20:44
tqtranthe part about us taking over the repo is what im proposing.20:44
tqtranthe other part, i think we should investigate first20:44
david-lyleI'm fine in or out20:45
r1chardj0n3sI think it makes sense for us to take over the repo with a separate set of cores specific to the project (even if that set is just shuu)20:46
r1chardj0n3sThat reduces the inherited burden for the current Horizon team.20:46
tqtranworse case, no one maintains it. we're back to square one, didnt lose anything.20:47
david-lylethe easiest first step for sure20:47
david-lyleand if gets dusty we just drop repo support20:47
*** matrohon has quit IRC20:47
tqtranand if someone needs plugin setup, we have a doc that points them to the repo and how to use it. easy peasy20:47
clu_i think it's a plus, a good starting pt for newcomers20:47
robcresswellTo be clear; does this actually *work* right now? and how?20:48
robcresswellah, via https://github.com/audreyr/cookiecutter20:49
r1chardj0n3syep20:49
tqtranhttp://docs.openstack.org/developer/tempest/plugin.html#plugin-cookiecutter20:49
tqtranheres what tempest does for their test plugin20:50
tqtranessentially, they have a patch for docs that guide users on how to use it20:50
*** haleyb_ has joined #openstack-meeting-320:50
r1chardj0n3stqtran: would you like to be the approver-shepherd for the ui-cookiecutter BP?20:50
tqtranyes please20:50
robcresswellCool, sounds good20:50
r1chardj0n3sgo for it, with the understanding that it's currently approved for being a project with the proviso I've noted in the BP, and that further investigation is needed regarding Horizon integration :-)20:51
tqtrani dont think the plugin shuu has is complete, its probably missing a few things like translation but we can add to that20:51
tqtranok, i'll start the process20:51
r1chardj0n3scool20:52
robcresswell\o/20:52
r1chardj0n3sok, we have a few minutes - do we have anything else anyone would like to bring up?20:52
r1chardj0n3sJust to note that the weekly Keystone-Horizon meeting will be tomorrow, at the same time as this meeting (2000 UTC) in #openstack-cp20:52
robcresswellr1chardj0n3s: I had an item on there20:53
robcresswellmight need to refresh the page20:53
*** rtheis has quit IRC20:53
r1chardj0n3s#link https://etherpad.openstack.org/p/ocata-keystone-horizon the etherpad for the keystone/horizon meeting20:53
r1chardj0n3srobcresswell: ack! you snuck it in! go for it :-)20:53
r1chardj0n3s#topic gettext in JS - angular gettext? global gettext? text-shim.js?20:53
*** openstack changes topic to "gettext in JS - angular gettext? global gettext? text-shim.js? (Meeting topic: horizon)"20:53
r1chardj0n3sI think the answer is "yes?" :-)20:54
tsufievr1chardj0n3s, I have kind of status update on 'fixing integration tests' - the one I already mentioned to you20:54
robcresswellSo, in sorting out tox/run_tests, I kinda realised how much of our i18n infra is fractured20:54
*** bobmel has quit IRC20:54
robcresswellwe seem to have this test-shim(?) that allows global gettext, we have angular-gettext which is used in half a dozen places, and then all our commands are just bash scripts, which are hardcoded to o_d and horizon so plugin code cant use them20:54
robcresswellSo I've mostly fixed the hard coded extraction etc.20:55
*** haleyb_ has quit IRC20:55
robcresswellBut I'm really confused by the direction with test-shim and angular-gettext; I was hoping someone could explain.20:55
r1chardj0n3srobcresswell: angular-gettext provides the angular templating translation mechanisms20:55
robcresswellAre we ever going to remove that shim?20:55
tqtranso theres two part to i18n, the message extraction and message substitution20:56
robcresswellMaybe Im confusing it with the gettext angular module, which some parts include.20:56
tqtranangular-gettext is the substituion part20:56
robcresswellsome use gettext globally20:56
r1chardj0n3sI'm not familiar with the test-shim20:56
r1chardj0n3sgettext global is used by JS code20:56
tqtranright, django embeds a catalog object containing the gettext function20:56
tqtranwhich is globally available20:56
*** Swami has quit IRC20:56
tqtranbut within anguar modules, we have a wrapper gettext that we encourage people to use20:57
tqtranboth have to exist (since we still have legacy js code)20:57
robcresswellSo, how does that wrapper work? And why dont we actually use it?20:57
tqtranthe wrapper uses the global gettext underneath it all20:57
robcresswellAnd why does it have to imported as 'gettext'? Because that prevents use of ngettext etc.20:57
tqtranwe do use it, all of the angular code injects it20:58
*** krtaylor has quit IRC20:58
tqtranit has to be 'gettext' because of the message extraction part20:58
robcresswellmost of the modules are using the global one :/20:58
tqtranwe are using babel, and babel looks specifically for gettext20:58
tqtranif they are, then it is incorrect and should be using the injected gettext20:58
robcresswellokay, got that part20:59
*** Swami has joined #openstack-meeting-320:59
robcresswellIll continue this in #horizon20:59
r1chardj0n3ssorry folks, we are out of time :-(20:59
tsufievnp20:59
r1chardj0n3sthanks everyone for coming, and let's continue the gettext discussion in #horizon20:59
tqtranthe test-shim is there so we can use gettext in our tests (its just a mocked version) - though its been a while and i might be totally wrong here20:59
r1chardj0n3s#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Wed Nov 16 21:00:04 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-11-16-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-11-16-20.00.txt21:00
*** tsufiev has left #openstack-meeting-321:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-11-16-20.00.log.html21:00
dansmith#startmeeting nova_cells21:00
openstackMeeting started Wed Nov 16 21:00:15 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
dansmithwudup.21:00
*** r1chardj0n3s has left #openstack-meeting-321:00
melwitto/21:00
*** ducttape_ has left #openstack-meeting-321:01
dansmithnobody else?21:01
*** tqtran is now known as tqtran-afk21:01
med_here21:01
melwittmriedem must be in the middle of something21:01
dansmithgood, it was going to be awkward21:01
* med_ was drug into the meeting21:02
dansmith#topic testing and stuff21:02
*** openstack changes topic to "testing and stuff (Meeting topic: nova_cells)"21:02
dansmithanything here?21:02
melwittI have noticed more than usual failures in the cells v1 job21:02
*** robcresswell has left #openstack-meeting-321:02
melwittbut I don't know what they were21:02
dansmithreally? a bunch of stuff has been failing more than normal, so maybe it's unrelated to the actual cellsness?21:03
melwittyeah, I was about to say that too. there have been lots of random failures lately in other jobs as well21:03
dansmithaye21:03
dansmithon the general topic of testing I can say that I'm struggling with the v2 patch series right now, all in the name of testing21:04
dansmithand will probably end up with a slightly less realistic test scenario to begin with,21:04
dansmithand lean on tempest jobs to keep us honest21:04
melwittI wasn't sure if we'd talk about that under this  topic but that makes sense. I too have been experimenting still21:04
dansmithI talked to alaski this morning and he said he was planning to do the same21:04
*** makowals_ has quit IRC21:05
dansmithmelwitt: anything to report or just that it be tough?21:05
melwittdansmith: I seem to be making progress on a new fixture I'm trying that switches between in-memory sqlite DBs. but that could all come crashing down in the end. I'm still in the middle of running it with the servers tests21:06
dansmithorly21:07
dansmithlet me go ahead and:21:07
dansmith#topic reviews21:07
*** openstack changes topic to "reviews (Meeting topic: nova_cells)"21:07
melwittbasically because of some laziness on my part in the DB API, things aren't so patchable for testing. so I'm going through and adding 'pick_context_manager' on things that don't have it so that my patching/switching works in my fixture21:07
dansmithSo I've been avoiding the test thing for a bit and have been trying to get the refactor parts of that series landed first,21:08
dansmithwhich will give us more time to explore some of these other solutions21:08
dansmiththe gate has been kindof the suck, so haven't gotten much done, but a couple things have landed21:08
dansmithmelwitt: cool21:08
*** gugl has quit IRC21:08
melwittyeah, think we got 3 or 4 things at least approved21:09
dansmithyeah21:09
dansmithwell, counting the bits mriedem did for sure21:10
dansmithanyway, that one is coming along but it's slow21:10
dansmithany other series that need discussing?21:10
melwittyeah I was thinking of the total21:10
*** alaski has joined #openstack-meeting-321:10
melwittI need to but haven't yet updated the cells quota stuff spec21:10
dansmithokay21:11
melwittto change it to the counting approach and put the details from the etherpad in it21:11
dansmithcool21:11
*** uxdanielle has joined #openstack-meeting-321:12
dansmith#topic open discussion21:12
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"21:12
* melwitt sees a lascii21:12
dansmithI'm assuming no meting next week21:12
melwittoh, right. turkey week21:12
dansmithokay well, I don't really have anything else21:13
melwittI can't think of anything else either right now21:13
dansmithalaski: med_: anything?21:14
melwittI still haven't gotten around to getting that info on consoleauth and what the upcall is21:14
med_nada.21:14
melwittit's basically compute needs to call up to the consoleauth service to validate tokens21:14
dansmithoh right21:14
alaskinothing from me atm21:14
melwittand that's not been accounted for at all in our stuff yet21:14
alaskiI thought consoleauth was moving into the cells?21:15
melwittjust something I don't want to forget about21:15
dansmithack21:15
melwittPaulMurray wasn't at the summit as far as I'm aware and I was super sick that week, so we didn't get to talk about it21:15
dansmithyeah21:15
alaskigotcha21:15
*** mickeys has joined #openstack-meeting-321:15
*** bpokorny has quit IRC21:16
dansmithalaski: we had a more productive meeting last week, this week there just isn't much else to talk about.. just in case you're disappointed :)21:16
dansmithanyway, move to adjourn?21:16
med_2dd21:16
alaskiheh, not disappointed21:16
*** bpokorny has joined #openstack-meeting-321:17
dansmithwoot21:17
dansmith#info No meeting next week because: turkey21:17
dansmith#endmeeting21:17
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:17
openstackMeeting ended Wed Nov 16 21:17:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:17
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-11-16-21.00.html21:17
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-11-16-21.00.txt21:17
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-11-16-21.00.log.html21:17
*** mickeys has quit IRC21:20
*** bpokorny_ has joined #openstack-meeting-321:21
*** bpokorny has quit IRC21:23
*** mickeys has joined #openstack-meeting-321:28
*** gugl has joined #openstack-meeting-321:29
*** krtaylor has joined #openstack-meeting-321:33
*** tonytan4ever has quit IRC21:36
*** krtaylor has quit IRC21:37
*** gouthamr has quit IRC21:37
*** jdwald has joined #openstack-meeting-321:41
*** krtaylor has joined #openstack-meeting-321:45
*** krtaylor has quit IRC21:47
*** krtaylor has joined #openstack-meeting-321:50
*** irenab has joined #openstack-meeting-321:50
*** haleyb_ has joined #openstack-meeting-321:51
*** uxdanielle has quit IRC21:52
*** krtaylor has quit IRC21:53
*** alexismonville has quit IRC21:54
*** irenab has quit IRC21:55
*** haleyb_ has quit IRC21:56
*** krtaylor has joined #openstack-meeting-321:56
*** logan- has left #openstack-meeting-321:57
*** krtaylor has quit IRC21:59
*** krtaylor has joined #openstack-meeting-321:59
*** pvaneck has quit IRC22:01
*** pvaneck has joined #openstack-meeting-322:01
*** pvaneck has quit IRC22:02
*** pvaneck has joined #openstack-meeting-322:02
*** clu_ has quit IRC22:04
*** lblanchard has quit IRC22:04
*** clu_ has joined #openstack-meeting-322:04
*** julim has quit IRC22:05
*** betherly_ is now known as betherly22:10
*** lifeless has quit IRC22:11
*** lifeless has joined #openstack-meeting-322:12
*** s3wong has joined #openstack-meeting-322:12
*** slaweq_ has joined #openstack-meeting-322:25
*** absubram has quit IRC22:26
*** absubram has joined #openstack-meeting-322:37
*** galstrom_zzz is now known as galstrom22:38
*** jdwald has quit IRC22:40
*** kzaitsev_mb has joined #openstack-meeting-322:49
*** haleyb_ has joined #openstack-meeting-322:52
*** haleyb_ has quit IRC22:56
*** ErnestMillan has quit IRC22:59
*** logan- has joined #openstack-meeting-323:02
*** logan- has left #openstack-meeting-323:03
*** spzala has quit IRC23:03
*** kgarloff has left #openstack-meeting-323:07
*** krtaylor has quit IRC23:09
*** tqtran-afk is now known as tqtran23:13
*** reedip_ has joined #openstack-meeting-323:20
*** cleong has quit IRC23:20
*** kzaitsev_mb has quit IRC23:30
*** kzaitsev_mb has joined #openstack-meeting-323:32
*** galstrom is now known as galstrom_zzz23:34
*** claudiub has joined #openstack-meeting-323:38
*** irenab has joined #openstack-meeting-323:38
*** irenab has quit IRC23:43
*** david-lyle_ has joined #openstack-meeting-323:50
*** david-lyle has quit IRC23:51
*** haleyb_ has joined #openstack-meeting-323:53
*** rbak has quit IRC23:53
*** Swami has quit IRC23:58
*** reedip_ has quit IRC23:59
*** haleyb_ has quit IRC23:59
*** baoli has quit IRC23:59

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