Wednesday, 2016-12-14

*** galstrom_zzz is now known as galstrom00:00
*** singlethink has quit IRC00:01
*** bpokorny has quit IRC00:02
*** bpokorny has joined #openstack-meeting-300:02
*** baoli has quit IRC00:07
*** mtanino has quit IRC00:10
*** Patifa has quit IRC00:14
*** ativelkov has quit IRC00:15
*** galstrom is now known as galstrom_zzz00:16
*** ativelkov has joined #openstack-meeting-300:17
*** haleyb_ has joined #openstack-meeting-300:24
*** spzala has quit IRC00:26
*** kzaitsev_mb has joined #openstack-meeting-300:29
*** mariannelm has joined #openstack-meeting-300:30
*** harlowja has joined #openstack-meeting-300:30
*** dimtruck is now known as zz_dimtruck00:36
*** sdake has quit IRC00:45
*** rbak has joined #openstack-meeting-300:54
*** zz_dimtruck is now known as dimtruck00:55
*** sgrasley has joined #openstack-meeting-300:58
*** hoangcx has joined #openstack-meeting-301:01
*** kzaitsev_mb has quit IRC01:05
*** pvaneck has quit IRC01:05
*** rbak has quit IRC01:08
*** haleyb_ has quit IRC01:10
*** dimtruck is now known as zz_dimtruck01:11
*** shu-mutou-AWAY is now known as shu-mutou01:19
*** zz_dimtruck is now known as dimtruck01:20
*** markvoelker has quit IRC01:29
*** piet has joined #openstack-meeting-301:29
*** bpokorny_ has joined #openstack-meeting-301:32
*** bpokorny_ has quit IRC01:32
*** yamamoto has quit IRC01:33
*** huanxuan has joined #openstack-meeting-301:34
*** bpokorny has quit IRC01:35
*** haleyb_ has joined #openstack-meeting-301:37
*** ativelkov has quit IRC01:40
*** ativelkov has joined #openstack-meeting-301:40
*** haleyb_ has quit IRC01:41
*** tuanluong has joined #openstack-meeting-301:42
*** yamamoto has joined #openstack-meeting-301:52
*** dimtruck is now known as zz_dimtruck02:04
*** zz_dimtruck is now known as dimtruck02:15
*** yamamoto_ has quit IRC02:29
*** yamamoto_ has joined #openstack-meeting-302:30
*** baoli has joined #openstack-meeting-302:32
*** yamamoto_ has quit IRC02:35
*** lblanchard has quit IRC02:35
*** haleyb_ has joined #openstack-meeting-302:39
*** mariannelm has quit IRC02:41
*** haleyb_ has quit IRC02:43
*** haleyb_ has joined #openstack-meeting-302:43
*** Swami_ has joined #openstack-meeting-302:46
*** Swami has quit IRC02:48
*** Swami__ has quit IRC02:48
*** mrunge has quit IRC02:49
*** Swami has joined #openstack-meeting-302:49
*** bpokorny has joined #openstack-meeting-302:51
*** alexpilo_ has quit IRC02:52
*** mrunge has joined #openstack-meeting-302:54
*** bpokorny has quit IRC02:55
*** sdake has joined #openstack-meeting-302:55
*** sankarshan_away is now known as sankarshan03:00
*** sankarshan is now known as sankarshan_away03:06
*** sankarshan_away is now known as sankarshan03:06
*** VW has joined #openstack-meeting-303:06
*** yamamoto_ has joined #openstack-meeting-303:18
*** EmilienM has quit IRC03:19
*** EmilienM has joined #openstack-meeting-303:20
*** reedip has joined #openstack-meeting-303:23
*** yamahata_ has quit IRC03:24
*** bpokorny has joined #openstack-meeting-303:24
*** iyamahat_ has quit IRC03:24
*** coolsvap has joined #openstack-meeting-303:27
*** bpokorny has quit IRC03:29
*** markvoelker has joined #openstack-meeting-303:30
*** yamamoto_ has quit IRC03:31
*** markvoelker has quit IRC03:35
*** piet has quit IRC03:35
*** sdake has quit IRC03:44
*** prateek has joined #openstack-meeting-303:49
*** bpokorny has joined #openstack-meeting-303:55
*** bpokorny has quit IRC03:56
*** baoli has quit IRC03:57
*** Swami_ has quit IRC03:57
*** Swami_ has joined #openstack-meeting-303:57
*** pgadiya has joined #openstack-meeting-304:00
*** haleyb_ has quit IRC04:00
*** sdake has joined #openstack-meeting-304:01
*** hoangcx has quit IRC04:04
*** shu-mutou has quit IRC04:09
*** sdake_ has joined #openstack-meeting-304:10
*** sdake has quit IRC04:13
*** shu-mutou has joined #openstack-meeting-304:15
*** psachin has joined #openstack-meeting-304:18
*** haleyb_ has joined #openstack-meeting-304:19
*** haleyb_ has quit IRC04:19
*** bks has joined #openstack-meeting-304:22
*** huanxuan_ has joined #openstack-meeting-304:29
*** prateek has quit IRC04:31
*** sdake_ is now known as sdake04:40
*** sambetts_ has quit IRC04:43
*** sambetts_ has joined #openstack-meeting-304:44
*** sambetts_ is now known as Guest5156604:44
*** Guest51566 has quit IRC04:55
*** sambetts has joined #openstack-meeting-304:57
*** sdake has quit IRC05:00
*** anilvenkata has joined #openstack-meeting-305:03
*** huanxuan_ has quit IRC05:04
*** Swami_ has quit IRC05:06
*** Swami has quit IRC05:06
*** prateek has joined #openstack-meeting-305:09
*** prateek has quit IRC05:09
*** prateek has joined #openstack-meeting-305:14
*** VW_ has joined #openstack-meeting-305:19
*** VW has quit IRC05:19
*** lpetrut has joined #openstack-meeting-305:21
*** VW_ has quit IRC05:24
*** kaz has joined #openstack-meeting-305:26
*** yamahata_ has joined #openstack-meeting-305:28
*** soichi has joined #openstack-meeting-305:29
soichihi05:31
kazhi05:31
*** s3wong has joined #openstack-meeting-305:31
*** markvoelker has joined #openstack-meeting-305:31
soichihello05:34
*** markvoelker has quit IRC05:37
soichianyone else?  still waiting05:39
soichi#startmeeting taas05:42
openstackMeeting started Wed Dec 14 05:42:38 2016 UTC and is due to finish in 60 minutes.  The chair is soichi. Information about MeetBot at http://wiki.debian.org/MeetBot.05:42
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:42
*** openstack changes topic to " (Meeting topic: taas)"05:42
openstackThe meeting name has been set to 'taas'05:42
soichi#topic Loop detection of tap flows (to prevent creating a loop)05:42
*** openstack changes topic to "Loop detection of tap flows (to prevent creating a loop) (Meeting topic: taas)"05:42
soichii'd like to be remained this as a homework for all taas folks05:43
soichimay be homework during Christmas and/or New Year holidays :)05:43
kaz+105:44
soichi#topic End of year and New year holidays?05:45
*** openstack changes topic to "End of year and New year holidays? (Meeting topic: taas)"05:45
*** rajinir has quit IRC05:46
soichii will confirm taas floks whether we can have IRC meeting on next week05:48
soichii'm afraid that today's IRC is the last one on this year...05:48
-soichi- in 2017, i'd like to resume IRC meeting from 11th Jan.05:50
soichi#topic Open Discussion05:51
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"05:51
soichiit seems no more topics, so i'd like to close today's IRC05:55
soichi#endmeeting05:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:55
openstackMeeting ended Wed Dec 14 05:55:57 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-12-14-05.42.html05:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-12-14-05.42.txt05:56
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-12-14-05.42.log.html05:56
soichibye05:56
kazbye05:56
*** soichi has left #openstack-meeting-305:56
*** matjazp has quit IRC06:02
*** kaz has quit IRC06:04
*** lpetrut has quit IRC06:05
*** amotoki has joined #openstack-meeting-306:12
*** amotoki has quit IRC06:14
*** tuanluong has quit IRC06:16
*** Fdaisuke has quit IRC06:17
*** amotoki has joined #openstack-meeting-306:17
*** Fdaisuke has joined #openstack-meeting-306:18
*** tuanluong has joined #openstack-meeting-306:21
*** hurgleburgler has quit IRC06:27
*** hurgleburgler has joined #openstack-meeting-306:28
*** hurgleburgler has quit IRC06:28
*** s3wong has quit IRC06:32
*** kumarb has joined #openstack-meeting-306:44
*** bks has quit IRC06:47
*** matjazp has joined #openstack-meeting-306:48
*** matjazp_ has joined #openstack-meeting-306:49
*** matjazp has quit IRC06:52
*** yamamoto_ has joined #openstack-meeting-306:58
*** markvoelker has joined #openstack-meeting-307:00
*** yamamoto_ has quit IRC07:03
*** markvoelker has quit IRC07:06
*** iyamahat has joined #openstack-meeting-307:08
*** sankarshan is now known as sankarshan_away07:09
*** bks has joined #openstack-meeting-307:17
*** Ace___ has joined #openstack-meeting-307:17
*** bapalm has quit IRC07:18
*** yamamoto has quit IRC07:18
*** kumarb has quit IRC07:19
*** iyamahat has quit IRC07:24
*** andreas_s has joined #openstack-meeting-307:25
*** yamahata_ has quit IRC07:37
*** bapalm has joined #openstack-meeting-307:38
*** egallen has left #openstack-meeting-307:39
*** matjazp has joined #openstack-meeting-307:50
*** ralonsoh has joined #openstack-meeting-307:51
*** matjazp_ has quit IRC07:52
*** yamamoto has joined #openstack-meeting-307:56
*** sankarshan_away is now known as sankarshan07:56
*** sankarshan is now known as sankarshan_away07:58
*** yamahata_ has joined #openstack-meeting-307:59
*** pcaruana has joined #openstack-meeting-307:59
*** rmart04 has joined #openstack-meeting-308:03
*** ociuhandu has quit IRC08:05
*** MarkBaker has quit IRC08:07
*** reedip has quit IRC08:08
*** ccamacho has joined #openstack-meeting-308:10
*** iyamahat has joined #openstack-meeting-308:16
*** reedip has joined #openstack-meeting-308:22
*** matrohon has joined #openstack-meeting-308:27
*** abalutoiu has joined #openstack-meeting-308:45
*** dimtruck is now known as zz_dimtruck08:46
*** iyamahat has quit IRC08:51
*** sankarshan_away is now known as sankarshan08:53
*** shu-mutou is now known as shu-mutou-AWAY08:59
*** rossella_s has joined #openstack-meeting-309:00
*** markvoelker has joined #openstack-meeting-309:02
*** tuanluong has quit IRC09:02
*** tuanluong has joined #openstack-meeting-309:03
*** ianychoi has joined #openstack-meeting-309:05
*** markvoelker has quit IRC09:07
*** bogdando has joined #openstack-meeting-309:19
*** rossella_s has quit IRC09:31
*** rossella_s has joined #openstack-meeting-309:32
*** tuanluong_ has joined #openstack-meeting-309:34
*** tuanluong has quit IRC09:36
*** yamahata_ has quit IRC09:37
*** Ace___ has quit IRC09:43
*** lpetrut has joined #openstack-meeting-309:59
*** MarkBaker has joined #openstack-meeting-310:02
*** kumarb has joined #openstack-meeting-310:02
*** bks has quit IRC10:06
*** mickeys has quit IRC10:11
*** VW has joined #openstack-meeting-310:19
*** tuanluong_ has quit IRC10:24
*** VW has quit IRC10:24
*** bks has joined #openstack-meeting-310:28
*** sdake has joined #openstack-meeting-310:29
*** kumarb has quit IRC10:30
*** kumarb has joined #openstack-meeting-310:52
*** matrohon has quit IRC10:55
*** bks has quit IRC10:55
*** MarkBaker has quit IRC10:56
*** markvoelker has joined #openstack-meeting-311:02
*** markvoelker has quit IRC11:07
*** sdague has joined #openstack-meeting-311:08
*** mickeys has joined #openstack-meeting-311:12
*** yamamoto has quit IRC11:12
*** mickeys has quit IRC11:17
*** prateek_ has joined #openstack-meeting-311:21
*** prateek has quit IRC11:21
*** qwebirc40703 has joined #openstack-meeting-311:21
*** qwebirc40703 has quit IRC11:22
*** yamamoto has joined #openstack-meeting-311:26
*** kumarb has quit IRC11:33
*** galyna has joined #openstack-meeting-311:37
*** tellesnobrega has joined #openstack-meeting-311:42
*** bks has joined #openstack-meeting-311:43
*** huanxuan has quit IRC11:44
*** abalutoiu has quit IRC11:46
*** bks has quit IRC11:52
*** MarkBaker has joined #openstack-meeting-311:52
*** tellesnobrega has quit IRC11:55
*** galyna has left #openstack-meeting-311:59
*** tellesnobrega has joined #openstack-meeting-312:07
*** rtheis has joined #openstack-meeting-312:12
*** huanxuan has joined #openstack-meeting-312:14
*** prateek_ has quit IRC12:14
*** bobmel_ has quit IRC12:15
*** bobmel has joined #openstack-meeting-312:19
*** pgadiya has quit IRC12:28
*** ociuhandu has joined #openstack-meeting-312:29
*** sdake has quit IRC12:31
*** pgadiya has joined #openstack-meeting-312:40
*** tellesnobrega has quit IRC12:46
*** claudiub has joined #openstack-meeting-312:48
*** qwebirc50810 has joined #openstack-meeting-312:52
*** qwebirc50810 has quit IRC12:52
*** sagar_nikam has joined #openstack-meeting-312:58
*** sdake_ has joined #openstack-meeting-312:58
*** tellesnobrega has joined #openstack-meeting-312:59
claudiub#startmeeting hyper-v13:00
openstackMeeting started Wed Dec 14 13:00:33 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
claudiubanyone here?13:01
sagar_nikamHi13:01
claudiubhello :)13:01
sagar_nikamI hope you had a good vacation13:01
claudiubit was great, it was like a surprisingly long weekend :D13:01
*** pgadiya has quit IRC13:02
claudiubis someone else from your team joining?13:02
*** sdake_ is now known as sdake13:02
sagar_nikamno13:02
sagar_nikamwe can start13:02
claudiubcool13:02
claudiub#topic Neutron Hyper-V Agent13:02
*** openstack changes topic to "Neutron Hyper-V Agent (Meeting topic: hyper-v)"13:02
claudiubsoo there are a couple of things i'm working on for networking-hyperv13:03
*** markvoelker has joined #openstack-meeting-313:03
claudiubone of them are neutron trunk ports13:03
sagar_nikamok13:03
domi007hi all :)13:04
claudiubheey, long time no see :)13:04
claudiub#link https://wiki.openstack.org/wiki/Neutron/TrunkPort13:04
domi007indeed, sorry about that :) gonna listen in again from time to time13:04
claudiubneutron trunk ports have been implemented in newton, btw13:04
claudiuband it could have some nfv usecases13:05
domi007so there are still plans to support HyperV's networking instead of using OVS?13:05
claudiubdomi007: sure, good to have you back. :)13:05
claudiubdomi007: so, at the moment, we are supporting both.13:05
claudiubdomi007: and we are currently looking into the new networking model that came with windows server 201613:06
claudiubwhich would mean native support for vxlan networking, as well as l3 support13:06
claudiuband other features13:06
sagar_nikamso what is the change in Ocata.. if we have this already implemented in newton13:06
domi007oooo :) much has changed I see13:06
claudiubsagar_nikam: neutron trunk ports have been introduced in newton in neutron (linuxbridge and neutron-ovs-agent)13:07
claudiuband we didn't have that implemented in networking-hyperv13:07
*** markvoelker has quit IRC13:08
claudiubanyways. neutron trunk ports are not enabled in the neutron server by default.13:08
claudiubi had to find out that the hard way. :)13:08
claudiubyou'll have to add the TrunkPlugin in neutron.conf, something like this:13:09
claudiubservice_plugins = neutron.services.l3_router.l3_router_plugin.L3RouterPlugin,neutron.services.metering.metering_plugin.MeteringPlugin,neutron.services.trunk.plugin.TrunkPlugin13:09
claudiubjust fyi13:09
domi007good to know13:09
claudiubi didn't really find any information about this specific thing13:09
*** lpetrut has quit IRC13:10
claudiubthe other thing that i'll be looking into and implement pretty soon, would be networking qos13:10
claudiubyou can add qos policies to neutron networks13:10
*** sagar_nikam_ has joined #openstack-meeting-313:10
*** sagar_nikam has quit IRC13:11
claudiuband it was first introduced in neutron in liberty. so, i think it's about time to support this. :)13:11
claudiubhm, sagar dropped off. will wait for him for a bit13:11
*** sagar_nikam has joined #openstack-meeting-313:11
sagar_nikamHi.... I am back13:12
claudiubwb :)13:12
sagar_nikamgot disconnected13:12
sagar_nikamwe had a cyclone yesterday in my state... network services are badly affected13:12
sagar_nikami might be disconnected again13:12
claudiubooh, sorry to hear that13:13
sagar_nikami am safe... only bad network13:13
claudiubjust a small recap: the next feature: networking qos. will start working on it pretty soon. it was first introduced in liberty in neutron.13:13
claudiubsagar_nikam: that's good, people >> internet. :D13:13
sagar_nikamok13:13
claudiubany questions?13:14
claudiubabout this topic?13:14
sagar_nikamno13:14
claudiubcool. moving on.13:14
claudiub#topic nova staus13:15
*** openstack changes topic to "nova staus (Meeting topic: hyper-v)"13:15
claudiubno new patches merged on nova for us since last meeting, unfortunately.13:15
sagar_nikamok13:15
claudiubregarding the nova-ovs ci, if you are curious, here are some test results: http://64.119.130.115/debug/nova-ovs/results.html13:16
claudiubthe test failures are unrelated, they are a bit flaky, because of tempest13:17
sagar_nikamchecking13:17
claudiubthey are being re-run currently.13:17
sagar_nikamany perf improvement as compared to hyperv switch ?13:18
claudiubthe hyper-v ci doesn't test performance, it only runs tempest13:19
claudiubso, it won't be able to tell any performance difference between neutron-ovs-agent and neutron-hyperv-agent13:19
sagar_nikamok.. got it13:19
*** sdake_ has joined #openstack-meeting-313:20
claudiubsagar_nikam: also, what do you mean by performance: the VM's network throughput, or the VM spawn time?13:20
claudiubanyways, I mentioned last time that I was having some weird issue regarding the neutron-ovs-agent13:21
domi007hm what was that?13:22
claudiubthat it would sometimes "freeze", and wouldn't process ports anymore, but it would still send its alive state to neutron13:22
sagar_nikamcould you find the root cause ?13:23
*** sdake has quit IRC13:23
claudiubyep13:23
sagar_nikamok... what was it13:23
domi007oo I see13:23
claudiubmanaged to find a deterministic rule to reproduce it as well13:23
claudiubalso, this issue doesn't appear prior to newton13:23
claudiubsoo.. in newton, the default values of a new neutron conf options changed13:24
*** markvoelker has joined #openstack-meeting-313:24
claudiubin particular: of_interface changed from "of_interface" to "native" and ovsdb_interface changed from "vsctl" to "native"13:25
sagar_nikamok13:25
claudiubwe currently do not support the "native" interface, unfortunately. but we are currently working on it, and it will most probably be included in the next windows ovs release13:26
domi007okay, any timeline on that?13:26
claudiubso, until then, bear in mind, if you upgrade to newton or newer, you'll have to have these config options on the neutron-ovs-agent's neutron.conf files:13:27
domi007also is it gonna be a new major version?13:27
claudiub[ovs]13:27
claudiub...13:27
claudiubof_interface = ovs-ofctl13:27
claudiubovsdb_interface = vsctl13:27
domi007okay, so there is a workaround :)13:27
claudiubyep :)13:27
claudiubjust have these config options and you'll be fine.13:27
sagar_nikamok got it.. as of now we are still in the process of upgrading to mitaka... so not so much of a issue for us for sometime13:28
domi007great, thanks13:28
*** sdake_ is now known as sdake13:29
claudiubdomi007: most probably next minor version release. we are currently on 2.6.. so 2.713:29
claudiubas for timeline, we follow the same release timeline as the ovs timeline13:30
domi007okay, good :) thank you13:30
claudiuband just fyi: functionally, there is no difference between the "native" and "vsctl / ovs_ofctl" interfaces. they do the same thing.13:31
domi007sure :)13:31
claudiubthe difference is in performance. the vsctl / ovs_ofctl interface does sys exec calls, while the native one connects to a tcp socket opened by ovs13:31
*** rossella_s has quit IRC13:31
claudiubs/performance/execution time13:32
*** rossella_s has joined #openstack-meeting-313:32
claudiubany questions on this subject?13:32
domi007not from me13:33
sagar_nikamno from me13:33
claudiubcool. :)13:33
claudiub#topic Hyper-V Cluster updates13:33
*** openstack changes topic to "Hyper-V Cluster updates (Meeting topic: hyper-v)"13:33
claudiubjust a minor update: we've found a few bugs, we've submitted their fixes13:34
claudiubwill link to them shortly13:34
sagar_nikamgerrit link ?13:34
claudiubyep. gerrit seems down to me13:34
sagar_nikamthe last time (which is few months back) we had tried your patch. it worked quite well13:35
claudiubsagar_nikam: that's good to hear. :)13:35
sagar_nikamwe can try it again once you give the gerrit13:35
sagar_nikamand everything is fixed13:35
claudiubthose bugs are minor, and quite edge case, but it's still good to have the fixes and know about them13:36
sagar_nikamok13:36
sagar_nikamand what happened to cinder-volume suppprt ?13:36
claudiubok. first one is a very minor one. it happens if you have any non-nova clustered vms. the hyper-v cluster driver was trying to failover them as well, and it shouldn't.13:37
claudiub#link https://review.openstack.org/#/c/406131/13:37
claudiubthe second one: the nova-compute service listens to failover events, but if  the service is down for any reason, and a failover occurs during that period, it won't be able to process those failovers, meaning that if any instance failovered to the "current" host, the nova-compute service couldn't let nova know about it13:39
claudiuband nova would still consider it on the "old" host.13:40
claudiub#link https://review.openstack.org/#/c/406069/13:40
sagar_nikamwill check and get back13:40
claudiubthe first one was merged on master, newton, and mitaka13:40
claudiubthe second one, there's a minor comment that i'll have to address.13:41
claudiubsagar_nikam: also, what did you mean about the cinder-volume support?13:41
sagar_nikamnova instances having cinder volumes attached to instances running on the cluster13:42
sagar_nikamif failover happens13:42
sagar_nikamthe volumes are not migrated13:43
claudiubit always worked with smb volumes.13:43
sagar_nikami think instances are not migrated since it has volumes13:43
sagar_nikami meant iscsi volumes... i should have been clear13:43
claudiubas for iscsi, it is in the pipeline at the moment13:44
sagar_nikamok13:44
sagar_nikamlet me know if you get it working13:45
sagar_nikamalso last time we used your patch... it was submitted upstream in nova13:45
sagar_nikamthese 2 new patches you mentioned are in compute-hyperv13:45
claudiubsure, but it take some time to get it right13:46
claudiubsagar_nikam: yep, they are in compute-hyperv13:46
sagar_nikamwill these patches work as is in nova upstream ?13:46
sagar_nikamafter i apply your previous patch which we have tested13:46
claudiubyeah13:46
*** slaweq has joined #openstack-meeting-313:47
sagar_nikamok... will let you know how it progress13:47
claudiubcool, ty. :)13:48
sagar_nikamin the meanwhile if you get iscsi support working, let me know, i will apply that patch as well and test13:48
claudiubsagar_nikam: yep, will do. :)13:48
claudiubanything else on this topic?13:48
sagar_nikamno13:49
*** julim has joined #openstack-meeting-313:49
claudiub#topic open discussion13:49
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:49
claudiubany news from you folks? :)13:49
domi007nothing really :)13:50
sagar_nikamyes.. i have started raising tickets to get us moving with mitaka with the ops team13:50
sagar_nikamfirst thing... we need to clone os-win in our downstream repo13:50
domi007we're gonna get new hw around february, gonna transition to openstack-ansible and hyperv 201613:50
sagar_nikami have a question on os-win13:50
claudiubawesome :)13:51
sagar_nikamwe will use stale/mitaka13:51
claudiubsagar_nikam: sure, go ahead13:51
sagar_nikamif you find bugs in ocata... do you plan to fix them in stable/mitaka as well ?13:51
*** lpetrut has joined #openstack-meeting-313:52
claudiubsagar_nikam: yep, while respecting the general openstack policy13:52
sagar_nikamok13:52
*** abalutoiu has joined #openstack-meeting-313:53
*** srobert has joined #openstack-meeting-313:53
*** ibmko has quit IRC13:53
claudiubwhich means that currently, i'm backporting all bug fixes to newton, and to mitaka, primarely high impact / low risk bug fixes13:53
sagar_nikami will take some time for us to get going with mitaka as creating downstream repos will take time13:53
sagar_nikamwill keep you posted13:53
sagar_nikamnext question13:54
claudiubsure13:54
sagar_nikamany news on this13:54
sagar_nikamhttps://github.com/FreeRDP/FreeRDP-WebConnect/issues/14913:54
*** baoli has joined #openstack-meeting-313:55
claudiubit seems that there's some problem with cpprestsdk13:56
*** tongli has joined #openstack-meeting-313:56
sagar_nikamyes.. remember that .. had discussed with c64cosmin:13:57
claudiuband it can't do https requests to keystone13:57
claudiubhe tried with a newer cpprestsdk, but the problem persists.13:57
sagar_nikamany fixes planned ?13:57
sagar_nikamok13:57
*** tongli has left #openstack-meeting-313:58
*** jjung has joined #openstack-meeting-313:59
*** krtaylor has joined #openstack-meeting-313:59
claudiubhm, other than that, I don't have any other info on this matter13:59
claudiubany other questions?13:59
sagar_nikamok13:59
sagar_nikamtime almost over13:59
sagar_nikamno...13:59
sagar_nikamthanks for attending13:59
claudiubthanks for joining. :)14:00
claudiubsee you next week!14:00
claudiub#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Dec 14 14:00:16 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-12-14-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-12-14-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-12-14-13.00.log.html14:00
ralonsoh#startmeeting neutron_qos14:00
openstackMeeting started Wed Dec 14 14:00:37 2016 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:00
openstackThe meeting name has been set to 'neutron_qos'14:00
ralonsohHi14:00
claudiubo/14:01
*** davidsha has joined #openstack-meeting-314:01
ralonsohLet's wait one minute14:01
davidshaHi14:01
*** alexismonville has joined #openstack-meeting-314:01
ralonsohhi davidsha14:01
ralonsohok, let's start...14:02
ralonsoh#topic RFEs14:02
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"14:02
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/163479814:02
openstackLaunchpad bug 1634798 in neutron "[RFE] Qos DSCP to vlan priority mapping" [Wishlist,Confirmed]14:02
ralonsohAny volunteer?14:03
davidshaOne sec14:03
davidshaThat's dependent on this right? https://bugs.launchpad.net/neutron/+bug/150563114:04
openstackLaunchpad bug 1505631 in neutron "[RFE] QoS VLAN 802.1p Support" [Wishlist,Confirmed] - Assigned to Kannan Raman (kannanrc20)14:04
ralonsohBut should be merged now14:04
ralonsohlet me check14:04
ralonsohok, not yet14:05
davidshaIt just has the spec atm14:05
ralonsohso maybe could be interesting to review this patch14:05
slaweqhello14:05
slaweqsorry for late14:05
davidshaHi14:06
ralonsohhi, we were waiting for you14:06
ralonsohjust you, davidsha and me14:06
slaweqok :)14:06
*** abalutoiu_ has joined #openstack-meeting-314:06
ralonsohSecond RFE14:06
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/164436914:06
openstackLaunchpad bug 1644369 in neutron "Support for DSCP marking in Linuxbridge L2 agent" [Wishlist,Fix released] - Assigned to Slawek Kaplonski (slaweq)14:06
ralonsohMerged!!14:06
ralonsohCongrats14:06
slaweqthx14:06
*** sagar_nikam has quit IRC14:06
ralonsohVery fast14:06
davidshaI was looking at the spec but I was waiting for it to be moved from Ocata to Pike14:06
slaweqI was even supprised how fast it goes :)14:07
ralonsohdavidsha: yu are talking bout the DSCP patch?14:07
ralonsohspec14:07
davidsha802.1p14:07
ralonsohyes14:07
ralonsohok, so let's follow this spec and let's review it14:08
ralonsoh#link https://review.openstack.org/#/c/392023/14:08
slaweqabout this dscp and LB, I think it could be quite similar for sr-iov but I don't know sr-iov so I'm not sure about that14:08
davidshaIf I recall ip link could modify the ToS field but it was only for certain types of traffic14:09
ralonsohYes, I'll create a bug for DSCP and SRIOV14:09
*** abalutoiu has quit IRC14:09
ralonsohI'll investigate this14:09
slaweqralonsoh: thx14:09
slaweqI don't know sr-iov and I don't have dev environment to check it14:09
ralonsohThat maybe will depend on the specific driver14:09
ralonsohI'll check this14:09
ralonsohNext RFE14:10
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/157898914:10
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:10
ralonsohVery easy14:10
ralonsoh1) Spec14:10
ralonsoh#link https://review.openstack.org/#/c/396297/14:10
ralonsohWe need to have this spec approved14:10
ralonsohAnd first patch14:11
ralonsoh#link https://review.openstack.org/#/c/401254/14:11
ralonsohPlease, I need reviews!!14:11
davidshaI'll look at both asap14:11
slaweqabout this specs I had some doubts about that14:11
ralonsohOk, I'll try to ping ajo later14:12
ralonsohWhy?14:12
ralonsohWhich doubts?14:12
slaweqfor example what with live-migration?14:12
slaweqor updating rule which is already applied on some port14:12
ralonsohlive-migration: it will depends on the hardware availability14:13
ralonsohon the second compute node14:13
ralonsohIf you spawn new VM's on a new node, you'll update nova scheduler database14:13
*** iyamahat has joined #openstack-meeting-314:14
slaweqok, what about update rule?14:14
slaweqlet's say I have 10 vms, each with 10Mbps limit14:14
ralonsohThat's considered, please review the patch14:14
ralonsohcontinue, please14:14
slaweqok, I will check it again14:14
slaweqthx14:14
ralonsohno no, continue14:14
slaweqok14:14
ralonsohI see were are you going....14:15
slaweqso, then what if You will update to 20Mbps in rule?14:15
ralonsohYes14:15
slaweqYou will have overall not 100Mbps but 200Mbps14:15
slaweqand it can be too much on host14:15
ralonsohone option: to cancel this rule update14:15
ralonsohthis information is in the qos extension14:16
ralonsohso if you extend the needed bw beyond the maximun available, there should be an error14:16
ralonsohthat makes sense?14:16
slaweqok, maybe I didn't read it all, but will qos extension know about overall available/used bandwidth on host?14:16
ralonsohqos extension will14:17
ralonsoh1) read the initial bw14:17
slaweqisn't it in Nova?14:17
ralonsoh2) update this info14:17
ralonsoh3) inform nova14:17
slaweqok14:17
slaweqso forbid update can be some option14:17
ralonsohbut, that's my design. And I need ajo to review this!14:17
ralonsohok, let's move to bugs14:18
ralonsohanything else?14:18
slaweqbut I'm not sure if it will not be related to "improved validation" patch14:18
ralonsohhmmmm14:18
slaweqand this ajo's patch to refactor notifications14:18
ralonsohI need to review both patches14:19
slaweqwhat in case if You will have port without qos policy already on host and will do "port update" to add such QoS?14:19
ralonsohyes14:19
slaweqit should be also forbiden in such case14:19
slaweqso it can be quite hard to do now :/14:19
ralonsohwhy?14:19
slaweqmaybe not hard from technical point of view14:20
ralonsohif the needed bw doesn't exceed the available bw14:20
ralonsohit's ok14:20
slaweqbut it's similar problem like this "improved validation"14:20
slaweqplease talk with ajo about that14:20
ralonsohsure!14:20
ralonsohthanks!14:20
ralonsohlet's continue14:21
ralonsoh#topic Bugs14:21
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"14:21
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/164950314:21
openstackLaunchpad bug 1649503 in neutron "Mechanism driver can't be notified with updated network" [High,In progress] - Assigned to Hong Hui Xiao (xiaohhui)14:21
*** lblanchard has joined #openstack-meeting-314:21
ralonsoh#link https://review.openstack.org/#/c/410101/14:21
ralonsoharmax move the priotity to high14:22
ralonsohso we should take care of this one14:22
ralonsohwe should review the patch14:22
slaweqok, I will also try to review it14:22
slaweqit's not big patch :)14:22
ralonsohno, it isn't14:22
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/164951714:23
openstackLaunchpad bug 1649517 in neutron "qos policy attached to network, qos_policy_id is reflecting on neutron net-show , but not on the port with neutron port-show" [Wishlist,New]14:23
ralonsohfeedback from ajo14:23
slaweqI talked with ajo about it yesterday14:23
ralonsoh"to close as opinion"14:23
slaweqyep, ajo said that it's not a bug but feature :)14:23
slaweqbut personally I think that it could be something like "network_qos_policy" and "qos_policy" (or port_qos_policy) in port details14:24
slaweqto distinquish easily which policy is used on port14:24
ralonsohyes, I have the same opinion14:24
slaweqwhat You think?14:24
ralonsohbut the author should open it as a RFE14:25
slaweqyep14:25
ralonsohlet's wait for the author response14:25
slaweqok14:25
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/164950314:25
openstackLaunchpad bug 1649503 in neutron "Mechanism driver can't be notified with updated network" [High,In progress] - Assigned to Hong Hui Xiao (xiaohhui)14:25
ralonsohsorry14:26
ralonsohmy fault14:26
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/164948814:26
openstackLaunchpad bug 1649488 in neutron "Duplicated revises_on_change in qos models" [Low,In progress] - Assigned to Hong Hui Xiao (xiaohhui)14:26
ralonsohpatch in https://review.openstack.org/41006514:26
ralonsohOk, I see now it's almost merged14:26
ralonsohNext one14:27
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/164637014:27
openstackLaunchpad bug 1646370 in neutron "QosPolicyInUse after notifying the removal to backends" [Medium,In progress] - Assigned to Miguel Angel Ajo (mangelajo)14:27
ralonsohpatch https://review.openstack.org/#/c/405448/14:27
ralonsohlet's wait for ajo feedback...14:27
ralonsohbut we should review it14:27
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/164076214:28
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:28
ralonsohStill waiting for author feedback...14:28
*** yamahata_ has joined #openstack-meeting-314:28
slaweqyep, and I couldn't reproduce it14:28
ralonsohok, so no action now14:28
slaweqyes14:29
ralonsohok, last one14:29
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/163918614:29
openstackLaunchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed] - Assigned to Luis Tomas Bolivar (ltomasbo)14:29
ralonsohThat's a difficult one14:29
ralonsohqos on trunk ports14:29
ralonsohand I don't see a solution to fix the solution proposed https://review.openstack.org/#/c/397788/14:30
ralonsohIt's easy to use veth ports to connect bridges14:30
ralonsohbut the performance drops a lot14:30
ralonsohand it's not useful for user space ovs14:31
slaweqyep, there is nothing new here since last meeting14:31
*** tonytan4ever has joined #openstack-meeting-314:31
ralonsohI'll ask in launchpad if there is any movement on this14:31
slaweqok14:31
ralonsohOk, any other bug not listed??14:32
slaweqI don't have anything new14:32
ralonsohok14:32
ralonsoh#topic Other Changes14:32
*** openstack changes topic to "Other Changes (Meeting topic: neutron_qos)"14:32
ralonsohthere is nothing in the agenda for this14:32
ralonsohany comment?14:33
slaweqit's not related to QoS but can You have a look on https://review.openstack.org/#/c/409432/6 ?14:33
slaweqthx in advance14:33
ralonsohYes, of course. I'll put this in my todo list for today14:33
slaweqthx a lot14:33
davidshaSame14:33
slaweqthx davidsha14:34
ralonsoh#topic Open Discussion14:34
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"14:34
*** srobert has quit IRC14:34
ralonsohOSC: #link https://review.openstack.org/#/c/352477/14:34
ralonsohThis is for ajo and dtroyer14:34
ralonsohIt's been a while since I uploaded the first version14:34
*** abalutoiu_ has quit IRC14:34
ralonsohOpen question: how can a developer speed up the reviews of his patches?14:35
slaweqIMHO ask on IRC, and try to ask specified people and ask for review14:36
slaweqfrom my experience it helps :)14:36
davidshaI agree IRC.14:36
*** stevejims has joined #openstack-meeting-314:36
ralonsohok, but I still have patches submitted nine months ago14:36
* ajo is around now, reads the backlog14:36
ralonsohwe are almost finish14:37
ralonsohsorry14:37
ajoack :)14:37
ajofor https://review.openstack.org/#/c/405448/ I must change a testing detail and it's done, I was pulled out to do something else, but I finished it now.14:37
*** VW has joined #openstack-meeting-314:37
ralonsohcool14:37
*** VW has quit IRC14:37
ralonsohslaweq, davidsha14:38
*** VW has joined #openstack-meeting-314:38
ralonsohdo you mind if I ask ajo now about #link https://bugs.launchpad.net/neutron/+bug/157898914:38
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:38
*** MarkBaker has quit IRC14:38
davidshago ahead14:38
ralonsohThe spec, #link https://review.openstack.org/#/c/396297/14:38
ralonsohajo, Can you continue with the spec?14:39
ralonsohajo: and please, take a look at #link https://review.openstack.org/#/c/401254/14:39
ralonsohthat's all14:39
ajoI think the spec is done,14:39
ajoI probably should answer yamamoto's question14:39
ralonsohthanks!14:40
ajowhich I don't fully understand14:40
ralonsohme neither...14:40
ajomay be I should try to answer the question on the spec itself by making it more clear14:40
ralonsohno, I do14:40
slaweqbut we was talking here that it can be related to Your patch https://review.openstack.org/#/c/396651/ and "improved validation"14:40
*** stevejims has left #openstack-meeting-314:41
ralonsohthis one too!14:41
slaweqin case if e.g. port will be updated and new qos with strict min bw limit will be set for it14:41
ajoyeah, that one I must definitely continue working on it14:41
ajoI restarted it yesterday night14:41
ajoand I must send another PS between today and tomorrow14:41
*** marst has joined #openstack-meeting-314:41
slaweq:)14:41
ajosorry :/  I'm being the bottleneck14:42
*** sdake_ has joined #openstack-meeting-314:42
ralonsohno problem, ask for help if you need it14:42
ajoI'll ping you for reviews on new PS for https://review.openstack.org/#/c/396651/ , it's almost ready14:43
slaweqyeah, I can help also :)14:43
ajothank you ralonsoh slaweq , If I see myself stopped again I will ping you14:43
*** gouthamr has joined #openstack-meeting-314:43
ralonsohThis, this patch should be merged ASAP14:43
ajoyes14:43
slaweqor we will ping You :P14:43
ralonsohhehehe14:44
ralonsohmore topics?14:44
ajo:D14:44
ajoslaweq ralonsoh thanks ':D14:44
ajoslaweq ping or punch? :D14:44
*** andymaier has joined #openstack-meeting-314:44
ralonsohsecond option!14:44
slaweqajo: we will see ;)14:44
ajoCTCP punch14:44
* ajo makes irc protocol jokes, and thinks he's old now14:45
slaweq:)14:45
ralonsohok guys, I'll close the meeting14:45
*** sdake has quit IRC14:45
ralonsohsee you around!14:45
ajoThank you very much ralonsoh & slaweq14:45
slaweqthx14:45
davidshaThanks ralonsoh, see ya!14:45
ajoI'll read the log right away14:45
slaweqajo: and davidsha14:45
ajoand davidsha :D14:45
slaweq:)14:45
slaweqsee You14:45
ralonsoh#endmeeting14:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:46
openstackMeeting ended Wed Dec 14 14:46:03 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-12-14-14.00.html14:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-12-14-14.00.txt14:46
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-12-14-14.00.log.html14:46
*** rhochmuth has joined #openstack-meeting-314:46
*** sdake_ is now known as sdkae14:47
*** sdkae is now known as sdake14:48
*** MarkBaker has joined #openstack-meeting-314:49
*** rbak has joined #openstack-meeting-314:49
*** mtanino has joined #openstack-meeting-314:52
*** stevejims has joined #openstack-meeting-314:54
*** Reedip_ has joined #openstack-meeting-314:55
*** anilvenkata has quit IRC14:58
*** hoppalm has joined #openstack-meeting-314:58
*** Swami has joined #openstack-meeting-314:59
*** koji has joined #openstack-meeting-314:59
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Dec 14 15:00:04 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
*** abalutoiu_ has joined #openstack-meeting-315:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** hosanai has joined #openstack-meeting-315:00
rhochmutho/15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:00
rbako/15:00
*** cbellucci has joined #openstack-meeting-315:00
*** kamil has joined #openstack-meeting-315:00
*** dhague has joined #openstack-meeting-315:00
dirko/15:00
rhochmuthAgenda for Wednesday December 14 2016 (15:00 UTC)15:00
rhochmuth1.Grafana - meeting with Raintank15:00
rhochmuth2.Reviews:15:00
rhochmuth1.https://review.openstack.org/#/c/408813/15:00
rhochmuth3.Log API future for reads15:00
rhochmuth4.Can we uncap python-kafka ? http://lists.openstack.org/pipermail/openstack-dev/2016-December/108436.html15:00
rhochmuth5.New version numbers for Java components https://review.openstack.org/#/q/projects:openstack/monasca+topic:version15:00
rhochmuth6.Ocata 2 Milestone: 15 Dec15:00
rhochmuth7.Adding Promethues features to Monasca15:00
rhochmuth1.PromQL15:00
rhochmuth2.Alarms and notifications15:00
rhochmuth1.https://prometheus.io/docs/alerting/alertmanager/15:00
dhagueo/15:00
rhochmuth2.Grouping Alerts15:00
rhochmuth3.Alarm inhibition15:00
kamilo/15:00
kojio/15:00
hosanaio/15:00
cbelluccio/15:00
rhochmuthhi everyone15:00
*** slaweq has left #openstack-meeting-315:00
rhochmuthlooks like a good agenda today15:00
stevejimshi all15:00
rhochmuthand we have a number of people here which is great15:01
*** witek has joined #openstack-meeting-315:01
rhochmuthi'll probably be out the next two weeks though15:01
rhochmuthso, for next week, unless i'm at home at 8:00 AM doing nothing, i probably won't attend15:01
rhochmuthbut, you can never rule me out15:01
rhochmuthso, someone else should start the meeting next week15:02
rhochmuthso, let's go through the agenda15:02
rhochmuth#topic Grafana - meeting with Raintank15:02
*** openstack changes topic to "Grafana - meeting with Raintank (Meeting topic: monasca)"15:02
rbakThat's me15:02
rhochmuthrbak: is that u15:02
rbakAnyone who asked to be on last weeks email to Raintank may have already seen this15:03
rbakBut we've setup a meeting with them for anyone who wants to attend.15:03
*** hurgleburgler has joined #openstack-meeting-315:03
rbakIt's at 1630 UTC, so half an hour after this meeting ends15:03
*** lblanchard has quit IRC15:03
*** huanxuan has quit IRC15:03
witekwhere?15:03
rbakI don't have the link for the the meeting yet but it should be in the email and I'll post it here once I have it.15:04
rbakThey said they would send one out to us.15:04
rhochmuthhttps://plus.google.com/hangouts/_/raintank.io/openstack?hceid=ZHV0dEByYWludGFuay5pbw.pt93p3n8dpqq55i410e81c3aks15:04
dhagueHere's the link for the meeting: https://plus.google.com/hangouts/_/raintank.io/openstack?hceid=ZHV0dEByYWludGFuay5pbw.pt93p3n8dpqq55i410e81c3aks15:04
rbakGreat, thanks15:04
rbakThat's all I had.  Anyone is welcome to attend who wants to talk with them about Grafana.15:05
dhagueOne thing to mention up front:15:05
rhochmuthdhague: are we going to try and keep the kubernetes meeting after this meeting15:06
dhagueThey seem to be of the mindset that openstack support will be a support burden for which they are looking for subscriptions from users (i.e. us), instead of seeing it as a contribution from us which will help their product15:06
dhagueSo we may have some perusading to do, or at least compromising.15:06
*** jamesgu has joined #openstack-meeting-315:06
rbakGood point.15:07
rbakI'll add that they've started talking to Charter again, so I wouldn't get hopes up but we might be able to offer some leverage there.15:07
rhochmuthyes, they are a business15:07
*** lblanchard has joined #openstack-meeting-315:08
*** bklei has joined #openstack-meeting-315:08
bkleio\15:08
rhochmuthso, let's see what they say later today15:08
*** Rockyg has joined #openstack-meeting-315:08
rhochmuthdhague: are we still trying to meet after this meeting?15:09
dhaguerhochmuth: about the k8s meeting, jobrs rescheduled it for next week to avoid conflicts, but we could also move it to the new year if that's more convenient15:09
*** qwebirc10057 has joined #openstack-meeting-315:09
stevejimsIf there is still resistance, would it be worth suggesting a plugin-style approach, and maintain a plugin outside grafana?15:09
rhochmuththanks dhague15:09
rbakstevejims: I think they're thinking pluggable auth would be a good idea.15:09
dhaguestevejims: that would be great, except that Go doesn't really do plugins nicely15:10
stevejimsOk, that's good15:10
rhochmuthnot sure i wanted hoppal to have to wait that long, as he is in the midst of developign his plugin15:10
rbakRight, so I don't know how they're planning on doing the pluggable auth.15:10
rbakWe'll see what they say in the meeting.15:10
hoppalmI can do whenever works for everyone else15:11
rhochmuthbut as far as i'm concerned to the new year is fine with me15:11
stevejimsSounds good15:11
rhochmuthsplit brain15:11
*** psachin has quit IRC15:11
dhaguerhochmuth hoppalm: ok, I'll get jobrs to push it to the new year15:11
rhochmuthok, sorry for the change in plans, was hoping to resolve this15:12
dhaguesummary: prometheus mtg in new year, grafana meeting in 1:15 from now15:12
rhochmuthhoppal's promethues and kubernetes plugins are up for review if you have some comments15:12
rhochmuthcorrect15:12
rhochmuthdhague15:12
rhochmuth#topic review https://review.openstack.org/#/c/408813/15:13
*** openstack changes topic to "review https://review.openstack.org/#/c/408813/ (Meeting topic: monasca)"15:13
rbakAlso mine.15:13
*** gouthamr has quit IRC15:13
*** spzala has joined #openstack-meeting-315:13
rbakJust wanted to get some eyes on.15:13
rbakIt's been up for a week and only one comment.15:13
rhochmuthlooks like craig has +1'd15:14
rhochmuthand bklei15:14
rhochmuthso, i'm assuming ready to go15:14
rbakIt's a pretty simple patch15:14
*** anilvenkata has joined #openstack-meeting-315:14
rhochmuthif anyone else want to take a quick look and merge that would be great15:14
rhochmuthor add comments as appropriate15:15
*** gouthamr has joined #openstack-meeting-315:15
rhochmuth#topic Log API future for reads15:15
*** openstack changes topic to "Log API future for reads (Meeting topic: monasca)"15:15
stevejimsThis was my addition15:15
stevejimsI was hoping to raise the topic of the future of the log API15:16
rhochmuthhi stevejms, welcome to the monasca meeting15:16
rhochmuthdoes anyone want to take a crack at this one?15:16
stevejimsHi, thanks15:16
witekwe thought of doing this, but for now decided to implement multi-tenancy in Kibana plugin15:16
rhochmuthif not, i can15:16
stevejimsWe have looked at the Kibana plugin but it looks like the MT was reverted?15:17
rhochmuthso, obviousely we would like to see this added15:17
rhochmuthit isn't trivial15:17
rhochmuthdo to the prioritues and resources we don't have any immediate plans to add support for reading logs from the log api15:17
witekwe are in the process of adding this to devstack plugin15:18
witekhttps://github.com/FujitsuEnablingSoftwareTechnologyGmbH/fts-keystone/tree/multitenancy15:18
witekthe plan is:15:19
witek* update tempest tests for logs15:19
witek* create new repo for plugin15:19
witek* include in devstack-plugin15:19
stevejimsSounds promising - Would be there be interest in proposals for an API, if we (I) could put some time into it?15:20
stevejimsThe use case would be allowing logs to be displayed in Grafana, so quite focused15:21
rhochmuthi think the answer is yes, we are always interested in developers becoming involved with the project15:21
*** anilvenkata has quit IRC15:21
rhochmuthbut, we also need to coordinate15:21
rhochmuthwitek?15:21
witeksure15:22
rhochmuthAlso, I want to mention, if we ever get to adding reads to the log api, we would want to look at the Searchlight for code reuse/inspiration…15:22
witekwe can work together on API proposal15:22
*** notq has joined #openstack-meeting-315:22
rhochmuthSearchlight has an api for quierying ES, that handle multi-tenancy, filtering of in/out bound queries, and making sure that queries are secure15:23
stevejimsSounds good - happy to coordinate on a proposal15:23
rhochmuthstevejims: so my suggestion would be to submit a blueprint first15:23
rhochmuthalong with some API proposals15:23
*** sankarshan is now known as sankarshan_away15:24
rhochmuthi'm wondering if we want to try and use storyboard for something like this, rather than launchpad15:24
witekgood idea15:24
rhochmuththen we can review either in weekly meetings or in a separate time/place15:24
rhochmuthwitek: storyboard?15:24
stevejimsSure15:24
witekyes15:24
rhochmuthstevejims: are you familiar with storyboard?15:25
stevejimsAfraid not but can get familiar15:25
rhochmuthhttps://storyboard.openstack.org/#!/page/about15:25
rhochmuthwe need to add a monasca project to it i think15:26
rhochmuthhopefully that isn't hard15:26
rhochmuthso let's close on this for now15:26
rhochmuthi'll assume we'll give storyboard a try15:26
rhochmuthstevejims, looks like you have approval to get started on a proposal and review with the team15:27
stevejimsOK grand - thanks all15:27
rhochmuthwhere do you work, btw?15:27
rhochmuth#topic Can we uncap python-kafka15:28
*** openstack changes topic to "Can we uncap python-kafka (Meeting topic: monasca)"15:28
rhochmuthhttp://lists.openstack.org/pipermail/openstack-dev/2016-December/108436.html15:28
witekI have put that one15:28
stevejimsCompany is called StackHPC, we primarily do consulting work for Cambridge University on OpenStack15:29
rhochmuthcool, thanks15:29
witekthere is some pressure from requirements team and oslo.messaging to uncap python-kafka15:29
*** baoli has quit IRC15:29
*** hecliunyx_ has quit IRC15:30
rhochmuthmy understanding after talking to joe about this is that it isn't a great situation15:30
rhochmuththey want to bump the kafka library to the latest one15:30
rhochmuthhowever, it only supports async15:30
rhochmuththere is a SimpleConsumer, that is depreated in the library, that they want us to move to15:31
rhochmuthbut, there are a number of issues outstanding in SimpleConsumer too15:31
rhochmuthi guess there is a SimpleProducer too15:31
rhochmuthi would like to free the openstack oslo folks up too15:31
rhochmuthbut, this change puts us in a potentially bad situation15:32
rhochmuthas an alternative, we were thinking about moving to the confluent library15:32
rhochmuththen we could get out of everyone's way15:33
*** agatea has joined #openstack-meeting-315:33
rhochmuththoughts?15:33
witekconfluent is not in global-requirements though, right?15:33
rhochmuthright15:33
rhochmuthwe would have to get that added first15:34
rhochmuththen we could move15:34
witekdo they support sync?15:34
rhochmuthi don't think so, but i'm not positive15:34
rhochmuthso, it isn't exactly a trivial change15:35
rhochmuthjoe is out for the rest of the year i believe15:35
rhochmuthso, i can't check with him15:36
rhochmuthis there anything else to discuss on this right now15:37
*** zz_dimtruck is now known as dimtruck15:37
witekok, thanks for explaining, it seems complicated at that point15:37
rhochmuthyes, it is15:37
rhochmuthso, let's get back to this issue in the new year15:38
rhochmuth#topic New version numbers for Java components15:38
*** openstack changes topic to "New version numbers for Java components (Meeting topic: monasca)"15:38
rhochmuthhttps://review.openstack.org/#/q/projects:openstack/monasca+topic:version15:38
witekcould we bump the version numbers of Java components?15:38
rhochmuthsure15:39
bkleiok by us at charter15:39
witekthe tests should be passing if we merge in a right sequence15:39
rhochmuthso, if you want to shepherd it through that would be great15:39
rhochmuthmonasca-common needs to go first i guess15:40
witekyes15:40
rhochmuthok, i guess feel free to +215:41
witekthen thresh and persister15:41
*** Marcellin__ has joined #openstack-meeting-315:41
rhochmuthright15:41
rhochmuth#topic Ocata 2 Milestone: 15 Dec15:42
*** openstack changes topic to "Ocata 2 Milestone: 15 Dec (Meeting topic: monasca)"15:42
witekjust a reminder15:42
rhochmuthomg15:42
witek:)15:42
rhochmuthalready15:42
witekI'll create tags15:43
rhochmuthsounds great15:43
*** davidsha has quit IRC15:44
rhochmuth#topic Adding Promethues features to Monasca15:44
*** openstack changes topic to "Adding Promethues features to Monasca (Meeting topic: monasca)"15:44
rhochmuththis is my topic15:44
rhochmuthjust wondering if anyone else had any thoughts or ideas on this15:44
rhochmuthi have a little prometheus envy lately15:45
rhochmuthbut, at the same time, i think we have some compelling features, functionality and architecture with monasca15:45
rhochmuththe prometheus community is starting to look at areas like scale, clustering, monitoring-as-a-service15:46
dhagueit seems like everybody is getting in on the alerting act: prometheus, ceilometer, grafana, ...15:46
rhochmuthyes, there is a huge amount of overlap15:46
*** NobodyCam is now known as WeAreAllMiLan15:46
rhochmuthanyway, i'm looking at this area a bit, and trying to understand what could be or should be done15:48
rhochmuthjust wanted to mention that15:48
jamesguleverage ro replacement?15:48
*** WeAreAllMiLan is now known as NobodyCam15:48
jamesguor15:48
rhochmuthi think understand first15:49
dhaguewe have a working student who is doing his thesis on monitoring our "converged cloud" openstack-on-kubernetes setup. His report should be available early in the new year, and hopefully we can share it here. It covers prometheus and monasca, among other things15:49
*** lpetrut1 has joined #openstack-meeting-315:49
rhochmuthmy first thought is to try and add features to monasca to remain parity15:49
rhochmuththanks dhague15:49
rhochmuthi also did a comparison, but unfortunatly on the internal wiki15:49
notqa diff of the features would be useful.15:49
rhochmuthso, i'll try and get that published on the monasca public wiki15:50
*** Sukhdev has joined #openstack-meeting-315:50
stevejimsWhen I have talked to people about Prometheus the thing they like the most is the simple nature of it, but that is also it's biggest issue (scalability)15:50
jamesguthanks rhochmuth15:50
*** lpetrut has quit IRC15:51
*** lpetrut1 is now known as lpetrut15:51
rhochmuthi was going to mention that there are two companies, weaveworks and digitalocean that have leverage promethues15:51
rhochmuthhttps://github.com/digitalocean/vulcan15:51
*** ralonsoh_ has joined #openstack-meeting-315:51
rhochmuthhttps://github.com/weaveworks/cortex15:51
*** ralonsoh has quit IRC15:51
rhochmuthok, enough on that topic15:52
rhochmuth#topic open floor15:52
*** openstack changes topic to "open floor (Meeting topic: monasca)"15:52
*** claudiub has quit IRC15:52
rhochmuthi guess no other topics15:54
rhochmuthso, i'll end the meeting15:54
rhochmuththanks everyone15:55
dhaguethanks15:55
rhochmuthsee some of you in a few minutes15:55
witekthanks15:55
rhochmuth#endmeeting15:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:55
openstackMeeting ended Wed Dec 14 15:55:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-12-14-15.00.html15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-12-14-15.00.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-12-14-15.00.log.html15:55
*** hosanai has quit IRC15:55
*** abalutoiu_ has quit IRC15:55
kamilthanks15:55
*** qwebirc10057 has quit IRC15:55
*** kamil has quit IRC15:55
stevejimsthanks15:55
*** koji has quit IRC15:55
*** cbellucci has quit IRC15:56
*** bklei has quit IRC15:56
*** stevejims has left #openstack-meeting-315:56
*** agatea has quit IRC15:56
*** catherineD has joined #openstack-meeting-315:56
*** dhague has quit IRC15:56
*** Reedip_ has quit IRC15:57
*** gema has joined #openstack-meeting-315:59
*** tongli has joined #openstack-meeting-316:00
eglute#startmeeting defcore16:01
openstackMeeting started Wed Dec 14 16:01:08 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: defcore)"16:01
*** cleong has joined #openstack-meeting-316:01
openstackThe meeting name has been set to 'defcore'16:01
*** MarkBaker has quit IRC16:01
*** shamail has joined #openstack-meeting-316:01
egluteHello Everyone!16:01
shamailhi!16:01
*** gouthamr has quit IRC16:01
eglutehogepodge is traveling today, so he will miss this meeting16:01
catherineDo/16:01
egluteand markvoelker might be able to join us late16:02
luzCo/16:02
* markvoelker just walked in16:02
eglute#topic agenda16:02
*** openstack changes topic to "agenda (Meeting topic: defcore)"16:03
eglute#link https://etherpad.openstack.org/p/DefCoreRoble.616:03
eglute#chair markvoelker16:03
openstackCurrent chairs: eglute markvoelker16:03
Rockygo/16:03
*** diablo_rojo_phon has joined #openstack-meeting-316:03
*** srobert has joined #openstack-meeting-316:03
egluteI added an easy item to the top of the agenda16:03
egluteis everyone planning on attending meeting next week?16:04
*** gouthamr has joined #openstack-meeting-316:04
markvoelkerbtw eglute: the meeting name should be interopwg instead of defcore now. =)16:04
eglutesince it is a few days before Christmas16:04
eglutemarkvoelker should i end this and start again16:04
Rockyggood chance I won't make it16:04
shamailI will be out next week16:04
markvoelkerHmm...wouldn't hurt since we haven't really started beyond the first item yet I guess.16:04
markvoelkerHard to retrain muscle memory. =)16:05
shamaileglute: +1, this will ensure this meeting isn’t in the archives but active16:05
eglute#endmeeting16:05
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:05
openstackMeeting ended Wed Dec 14 16:05:27 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-12-14-16.01.html16:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-12-14-16.01.txt16:05
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-12-14-16.01.log.html16:05
eglute#startmeeting interopwg16:05
openstackMeeting started Wed Dec 14 16:05:33 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:05
*** openstack changes topic to " (Meeting topic: interopwg)"16:05
openstackThe meeting name has been set to 'interopwg'16:05
markvoelkerthanks eglute16:05
eglute#chair markvoelker16:05
openstackCurrent chairs: eglute markvoelker16:05
eglute#topic next week16:06
*** openstack changes topic to "next week (Meeting topic: interopwg)"16:06
*** gouthamr has quit IRC16:06
catherineDI won't be able to attned next week meeting16:06
shamailI will not be able to meetings until 1/416:06
eglute#link beginning of this meeting:  http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-12-14-16.01.html16:06
markvoelkerI'll be able to make the meeting next week, but sounds like I'll be in the minority...16:06
eglutei can make it as well, but we might not have quorum16:07
luzCI'll be out until 1/416:07
egluteand the 28th is out as as well16:07
gemao/16:07
gemaI am out until the 9th of Jan :D16:07
egluteluzC are you back on 1/4?16:07
gemabut I will come to the meeting if you guys have it on the 4th or so16:07
egluteI think we should try have a meeting on 1/416:08
gema+116:08
markvoelkereglute: ++ for 1/416:08
markvoelkerWe need to finish up the 2017.01 guideline, so I think it's important.16:08
egluteok, that is settled then, next meeting on 1/416:08
*** garloff has joined #openstack-meeting-316:08
egluteother comments?16:08
eglute#topic PTG16:09
*** openstack changes topic to "PTG (Meeting topic: interopwg)"16:09
markvoelker#info No meetings for the rest of December.  Meetings resume 1/4/2017.16:09
eglutejust a reminder, that we have space at PTG16:09
egluteplease start adding topics to #link https://etherpad.openstack.org/p/InteropWGAtlantaPTG16:09
luzCeglute yes16:09
garloffthanks, @markv16:09
eglute#topic 2017.01 guideline16:10
*** openstack changes topic to "2017.01 guideline (Meeting topic: interopwg)"16:10
egluteshamail thanks for submitting cinder patch16:10
shamailYou’re welcome16:11
Rockyg++16:11
eglute#link https://review.openstack.org/#/c/408427/16:11
*** matjazp has quit IRC16:11
Rockygit gets easier the more you do ;)16:11
eglutei looked at scoring, looked like the new capabilities didnt get scored high enough16:11
egluteto be added16:11
shamailAs you mentioned in the review, none of the capabilities scored high enough to be actually considered advisory but I added them based on the conversations16:11
markvoelkereglute: that was my take when I looked at it this morning too16:11
shamailv3 currently is not used in SDKs or tools16:11
shamailso that gives it a major ding16:12
Rockygadvisory might get the sdk project to start implementing code with them ;-)16:12
egluteif they are not scored high enough we can't add them i dont think16:12
markvoelkerSo this is one of those API-transition periods, really16:13
shamailvolumes-list-api-versions doesn’t qualify either and this one has another issue, there is no tempest test16:13
*** MarkBaker has joined #openstack-meeting-316:13
markvoelkerE.g. if we take "future direction" away from the v2's, some of them wouldn't make the cutoff either.16:13
shamailI had to add “tempest.api.volume.NEED_TEST” to make sure the json doesn’t break16:13
*** rmart04 has quit IRC16:13
markvoelkerBut v3 is basically v2 plus microversions16:13
eglutealso, "complete" also was not set16:13
shamailmarkvoelker: +116:13
markvoelkerSo tools that work with v2 work with v3 too for the most part16:14
markvoelker(they just have to actually call the v3 endpoint)16:14
egluteso would it be worth re-scoring them with tools set to 1?16:14
garloffmarkvoelker: which they get from the catalog, so they may not even notice ...16:14
*** matjazp has joined #openstack-meeting-316:14
eglutegarloff that is a good point16:14
markvoelkergarloff: well, some do, some don't. =)16:15
shamailexactly markvoelker16:15
markvoelkerSome are manually configured16:15
markvoelkerTo me it feels like a reasonable transition here is to make these advisory now so people are aware of the transition to v3.  We can decide in the next Guideline whether they're really ready to become required16:16
eglutemarkvoelker +116:16
eglutewould be good to make that note somewhere16:16
egluteso that we need to re-score them before making them required16:16
markvoelkerI think we'd also discussed leaving a comment/note in the Guideline somewhere explaining the v2/v3 transition16:16
markvoelker(that could also be published somewhere in more detail and more plain-English-y like on the interop webpage)16:17
shamailThat sounds reasonable16:17
eglutedoes schema allow for notes?16:17
garloffmarkvoelker: I would expect all tools to use the catalog for discovery -- would be more concerned about tools that check for known versions and error out if they find an unexpected one16:17
* garloff is wondering why the switch to microversions can not be done without v2->v3 transition16:18
markvoelkereglute: yes, we just have to be a bit creative16:18
markvoelkere.g. the Guidance section of designated sections, or the capability names, or....16:18
Rockygmarkvoelker, I agree we need to signal to dev the need to advance.  We might also want to start a ml thread and/or blog post?16:18
markvoelkerer, description field, not name field. But you get the point.16:19
eglute#action shamail markvoelker to get creative and leave notes on cinder about v316:19
shamailThx16:19
markvoelkergarloff: well, unfortunately reality is that the endpoints are manually configured in some cases.  E.g. devs have a config entry for their tool to set endpoints.16:20
markvoelkershamail: I'd suggest we use the "description" field for the time being. So for example: https://github.com/openstack/defcore/blob/master/2016.08.json#L42016:21
* garloff imagines a customer entering 20 endpoints for an installation that includes some of the BigTent projects ...16:21
shamailSounds good markvoelker, I’ll add a note to the scoring results and update the description to highlight the transitory nature.16:22
eglutethank you shamail!16:22
egluteanything else on cinder?16:22
markvoelkergarloff: I've literally seen it done. =)  But usually those sorts of things are only dealing with a few operations and don't need to touch 20 projects (in my experience anyway).  Painful, but there it is...16:23
eglutein that case moving on to swift16:23
eglute#link https://review.openstack.org/#/c/398428/16:23
eglutei updated the scoring based on markvoelker comments16:23
*** andymaier has quit IRC16:24
egluteobjectstore-container-metadata is used by both fog and jclouds as far as i could tell16:24
markvoelkereglute: I haven't looked at it since the new patchsets went up last night, but will do today16:24
eglutethank you markvoelker16:24
egluteeveryone, would appreciate your feedback16:25
egluteright now, we are looking to add 2 new capabilities to swift as advisory16:25
egluteobjectstore-info-reques and objectstore-container-metadata16:25
egluteany comments/questions on swift?16:26
eglutein that case, onto nova!16:26
eglute#link https://review.openstack.org/#/c/385781/16:26
eglutethanks shamail16:26
egluteshamail i have not looked at the new patch yet16:26
shamailMoved capabilities to advisory, fixed the HEAD lines that got mixed in there16:27
eglutebut looks like we are adding 3 new advisory16:27
egluteshamail i think you need to remove deprecated nova parts as well16:27
shamailAdding two news ones and one that was there at some point but vanished16:27
shamail"compute-auth-create", "compute-auth-get"?16:28
shamailetc.16:28
shamaileglute: Remove the ones that were already listed as depreciated in next.json?16:28
eglutemove deprecated to removed, remove removed16:29
eglutedoes that make sense?16:29
shamailSure does16:30
garloffsounds logical to me16:30
eglutethank you shamail! also commented on the patch16:30
*** outofmemory has joined #openstack-meeting-316:30
shamailthanks!16:31
egluteotherwise it looks good, 3 new capabilities16:31
egluteany other comments or questions on nova?16:31
egluteif not, looks like we covered everything for 2017.01 guideline that was outstanding16:32
egluteany other comments on the guideline?16:32
*** outofmemory is now known as reedip_16:32
eglute#name change16:33
eglutethanks everyone who worked on the name change!16:33
eglutehopefully everyone subscribed to the new mailing list16:33
egluteif not, please do so!16:33
eglute#link http://lists.openstack.org/cgi-bin/mailman/listinfo/interop-wg16:33
eglute#action everyone subscribe to the new mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/interop-wg16:34
egluteand i think everyone here already joined the new irc channel16:34
* markvoelker thinks it's time to remove the old one now16:34
eglutemarkvoelker any ideas how to remove it?16:35
markvoelkereglute: yeah, I can handle that16:35
*** andreas_s has quit IRC16:35
eglutecool, thank you markvoelker16:35
eglutehow about github repo?16:36
eglutehow can we rename that? is there a process?16:36
markvoelkereglute: I suggest we finish off 2017.01 before we do that.  Otherwise we'll have a bit of a mess with in-flight scoring patches16:36
eglutemarkvoelker oh good point16:37
eglute#action move github repo after 2017.01 passes16:37
Rockyg++16:37
eglutemarkvoelker you still have a couple outstanding writing things for rename, but no rush on that unless you are already done16:38
Rockygand yes, the process is to submit a patch to infra.16:38
eglutethanks Rockyg16:38
*** claudiub has joined #openstack-meeting-316:38
*** notq has quit IRC16:38
markvoelkereglute: I'm close. =)  Probably next week.16:38
egluteanything else on the renames?16:38
eglutethank you markvoelker!16:39
eglute#topic Documenting how projects can become part of Guidelines16:39
*** openstack changes topic to "Documenting how projects can become part of Guidelines (Meeting topic: interopwg)"16:39
eglutemarkvoelker is this also next week/after holidays?16:39
markvoelkerProbably after the holidays.  It's on the backburner in favor of the rename and 2017.01 stuff16:40
eglute:)16:40
eglutesounds good to me16:40
eglute#topic update co-chair election process16:40
*** openstack changes topic to "update co-chair election process (Meeting topic: interopwg)"16:40
egluteAt the beginning of the year i submitted a patch on co-chair election process that was less than ideal16:41
eglute#link https://github.com/openstack/defcore/blob/16668dddea39725088040fdef5404a656b24a606/doc/source/process/2016A.rst#guidelines-review-phase-b16:41
egluteregarding timing and how the elections happen16:41
eglutefor B4.5: "One DefCore CoChair needs to be elected by DefCore working group. Election quorum is composed of attendees present during the election meeting."16:41
eglutethis section needs to be changed to be a bit more vague16:42
gemaeglute: isn't the usual process to do email elections?16:42
eglutegema correct16:42
eglutethats what we ended up doing16:42
egluteso that is why we need to change the process document16:43
gemathen let's make it email election, it is fairer than being able to make it to a meeting, I think16:43
RockygCould use the definition of AUCs16:43
eglutei will try to submit a better patch16:43
eglutegema i agree16:43
egluteRockyg do you have a link to that16:43
* gema imagines Rockyg going through her email at the speed of light16:44
* eglute laughs16:44
shamailhttp://governance.openstack.org/uc/reference/charter.html (See the AUC section)16:44
shamailsaved you some searching Rockyg!16:44
RockygLol16:44
gemahaha16:44
eglutewell, in any case, i welcome all input on the election process. i will try to make it as close to the other OpenStack elections as possible16:45
eglutethank you shamail!16:45
RockygThanks shamail !  Especially since he is one of the authors16:45
shamailyou’re welcome Rockyg :)16:45
gemashamail: +116:46
eglutewe still have one more topic, so lets move on to RefStack, since elections are not happening this year :)16:46
eglute#topic RefStack16:46
*** openstack changes topic to "RefStack (Meeting topic: interopwg)"16:46
eglutego ahead catherineD16:46
catherineDThanks eglute:16:46
catherineDSo the https://refstack.openstack.org/#/ was updated last Friday ...16:47
catherineDit now provide vendor/product registration process ... also allow Foundation admin to mark/unmark a test as verified16:47
markvoelkerneat16:48
*** tongli has quit IRC16:48
eglutenice16:48
catherineDthe vendor/product info at this first phase is only available privately ... so the users can have a look of how it will look like16:48
catherineDwe will make those info pubilicly available sometime after the PTG16:49
gemacatherineD: great! I will probably go through the process of registering us soon16:50
catherineDeveryone please take a look ... and log comment, request, bug report in RefStacl launchpad16:50
eglutenice job RefStack team! thank you catherineD!16:50
catherineDgema: great thanks ...16:50
catherineDeglute: thank you I will let the RefStack team know16:51
egluteanything else catherineD?16:51
eglute:)16:51
catherineDpay attention to the https://refstack.openstack.org/#/user_results  once you log in16:51
egluteok!16:52
catherineDthis is how the test record will look like on a verified test results16:52
catherineDthat is all16:52
Rockygkewl16:52
eglutethank you catherineD!16:52
eglute#topic open floor16:52
*** openstack changes topic to "open floor (Meeting topic: interopwg)"16:52
egluteanything else folks?16:52
eglutein that case, we can end early!16:53
markvoelkerhappy holidays everyone!  See you in January..16:53
egluteEveryone, please review outstanding patches16:53
eglutethank you for a great year!16:54
markvoelker(and in gerrit before then, right????)16:54
egluteright markvoelker!16:54
catherineDHappy holidays!16:54
egluteHappy Holidays everyone!16:54
shamailThank you everyone, Happy Holidays!16:54
eglute#endmeeting16:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:54
openstackMeeting ended Wed Dec 14 16:54:54 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:54
gemahappy holidays!16:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interopwg/2016/interopwg.2016-12-14-16.05.html16:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interopwg/2016/interopwg.2016-12-14-16.05.txt16:54
openstackLog:            http://eavesdrop.openstack.org/meetings/interopwg/2016/interopwg.2016-12-14-16.05.log.html16:55
*** yamamoto has quit IRC16:55
*** shamail has quit IRC16:55
*** yamamoto has joined #openstack-meeting-316:57
Rockyghappy holidays!16:58
*** piet has joined #openstack-meeting-317:00
*** rajinir has joined #openstack-meeting-317:00
*** caboucha has joined #openstack-meeting-317:01
*** yamamoto has quit IRC17:02
*** VW_ has joined #openstack-meeting-317:03
*** VW_ has quit IRC17:03
*** VW_ has joined #openstack-meeting-317:04
*** VW_ has quit IRC17:04
*** VW_ has joined #openstack-meeting-317:05
*** piet has quit IRC17:05
*** lpetrut has quit IRC17:05
*** Patifa has joined #openstack-meeting-317:05
*** sdake has quit IRC17:05
*** VW has quit IRC17:06
*** reedip_ has quit IRC17:08
*** catherineD has left #openstack-meeting-317:13
*** MarkBaker has quit IRC17:17
*** sdake has joined #openstack-meeting-317:26
*** rpodolyaka is now known as rpodolyaka_afk17:27
*** sdake has quit IRC17:30
*** rossella_s has quit IRC17:31
*** rossella_s has joined #openstack-meeting-317:32
*** mariannelm has joined #openstack-meeting-317:35
*** baoli has joined #openstack-meeting-317:36
*** yamahata_ has quit IRC17:42
*** iyamahat has quit IRC17:44
*** piet has joined #openstack-meeting-317:45
*** Patifa has quit IRC17:47
*** ociuhandu has quit IRC17:50
*** yamamoto has joined #openstack-meeting-317:56
*** sgrasley has quit IRC17:58
*** Sukhdev has quit IRC17:59
*** yamamoto has quit IRC18:01
*** iyamahat has joined #openstack-meeting-318:04
*** ralonsoh_ has quit IRC18:04
*** Rockyg has quit IRC18:07
*** bobmel has quit IRC18:12
*** tobybot11 has joined #openstack-meeting-318:13
*** mickeys has joined #openstack-meeting-318:14
*** bobmel has joined #openstack-meeting-318:17
*** caboucha has quit IRC18:18
*** VW_ has quit IRC18:20
*** lpetrut has joined #openstack-meeting-318:21
*** david-lyle has quit IRC18:21
*** yamahata_ has joined #openstack-meeting-318:22
*** matjazp has quit IRC18:25
*** yamamoto has joined #openstack-meeting-318:26
*** yamamoto has quit IRC18:27
*** yamamoto has joined #openstack-meeting-318:27
*** yamamoto has quit IRC18:27
*** markvoelker has quit IRC18:29
*** david-lyle has joined #openstack-meeting-318:30
*** piet has quit IRC18:31
*** s3wong has joined #openstack-meeting-318:34
*** markvoelker has joined #openstack-meeting-318:35
*** rhochmuth1 has joined #openstack-meeting-318:37
*** rhochmuth has quit IRC18:39
*** lpetrut has quit IRC18:39
*** VW has joined #openstack-meeting-318:40
*** VW has quit IRC18:40
*** sdake_ has joined #openstack-meeting-318:41
*** VW has joined #openstack-meeting-318:41
*** diablo_rojo_phon has quit IRC18:50
*** lpetrut has joined #openstack-meeting-318:51
*** sdake_ has quit IRC18:51
*** Patifa has joined #openstack-meeting-318:53
*** s3wong has quit IRC18:54
*** marst has quit IRC19:16
*** marst has joined #openstack-meeting-319:16
*** coolsvap has quit IRC19:19
*** Sukhdev has joined #openstack-meeting-319:20
*** yamamoto has joined #openstack-meeting-319:28
*** lpetrut has quit IRC19:28
*** tobybot11 has quit IRC19:32
*** julim_ has joined #openstack-meeting-319:32
*** julim has quit IRC19:33
*** Swami has quit IRC19:33
*** Swami has joined #openstack-meeting-319:34
*** yamamoto has quit IRC19:36
*** bobmel has quit IRC19:37
*** bobmel has joined #openstack-meeting-319:37
*** bobmel has quit IRC19:39
*** sdake has joined #openstack-meeting-319:39
*** bobmel has joined #openstack-meeting-319:39
*** sdague has quit IRC19:43
*** robcresswell has joined #openstack-meeting-319:44
*** sdague has joined #openstack-meeting-319:46
*** pvaneck has joined #openstack-meeting-319:47
*** gugl has joined #openstack-meeting-319:50
*** liangy has quit IRC19:52
*** rhochmuth1 has quit IRC19:52
*** hoppalm has quit IRC19:53
*** r1chardj0n3s has joined #openstack-meeting-319:53
*** liangy has joined #openstack-meeting-319:55
*** sdake has quit IRC19:55
*** MeganR has joined #openstack-meeting-319:56
*** hoppalm has joined #openstack-meeting-319:56
*** tqtran has joined #openstack-meeting-319:56
*** sdake has joined #openstack-meeting-319:59
*** Swami_ has joined #openstack-meeting-320:00
*** ducttape_ has joined #openstack-meeting-320:00
ducttape_o/20:00
r1chardj0n3s#startmeeting horizon20:00
openstackMeeting started Wed Dec 14 20:00:36 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
*** Swami has quit IRC20:00
r1chardj0n3sducttape_ o/20:00
*** VW has quit IRC20:00
lcastello/20:01
betherlyo/20:01
rhagartyo/20:01
*** rdopiera has joined #openstack-meeting-320:02
rdopierao/20:02
r1chardj0n3sI'll start off with the usual20:02
*** ying_zuo has joined #openstack-meeting-320:02
r1chardj0n3s#topic Priority patches for review20:02
*** openstack changes topic to "Priority patches for review (Meeting topic: horizon)"20:02
r1chardj0n3s#link https://review.openstack.org/#/q/starredby:r1chardj0n3s%20AND%20status:open is the current set, please focus attention here if you can20:02
r1chardj0n3sif you have anything you believe should be getting attention on the priority list please let me know20:03
r1chardj0n3sWe've got about four weeks until feature freeze for Ocata20:03
ducttape_ediardo - did your css change for the overflow make it yet ?20:04
ediardoo/20:04
r1chardj0n3sAt this point, it looks like we're going to have a lot of trivial fix patches in.20:04
*** spzala has quit IRC20:04
ducttape_that *might* be something to consider too20:04
ediardoNOpe..20:05
*** VW has joined #openstack-meeting-320:05
ying_zuoI have a blueprint accepted for ocata. https://blueprints.launchpad.net/horizon/+spec/launch-instance-volume-quotas20:05
ducttape_k.   might need to touch base with hurgleburgler again.  that bug is not great.  thanks ediardo20:05
ying_zuoRight now there's only one patchset. Should that be one the priority list?20:05
r1chardj0n3sying_zuo: seems entirely reasonable to me! added :-)20:06
ying_zuoThanks Richard20:06
r1chardj0n3sducttape_: I don't have any of your quotas work in the list - should I?20:06
ediardothis could be a "trivial fix": https://review.openstack.org/#/c/409753/20:06
ducttape_the one quota thing, you have in the list r1chardj0n3s.   I'll talk w u after this meeting if avail20:07
rdopierar1chardj0n3s: I'd like some attention on that django config patch, if possible20:07
ducttape_my other stuff is not ready20:07
*** srobert has quit IRC20:07
r1chardj0n3sducttape_: ok20:07
r1chardj0n3srdopiera: is it ready for review?20:08
rdopierar1chardj0n3s: yes20:08
*** tsufiev has joined #openstack-meeting-320:08
rdopierar1chardj0n3s: https://review.openstack.org/#/c/404735/20:08
r1chardj0n3sok, cool! could you please add the patchsets to a section in https://etherpad.openstack.org/p/horizon-ocata-priorities Ocata-2/320:08
tsufievo/20:08
rdopieraadded20:09
r1chardj0n3sjust the one patch? ok :-)20:09
rdopierar1chardj0n3s: there are some cleanup patches, but they are independent and not as important20:10
r1chardj0n3srighto, that's what confused me20:10
r1chardj0n3sI'm easily confused ;-)20:10
rdopierain fact, they all conflict with each other...20:10
r1chardj0n3s\o/20:10
r1chardj0n3sso, in a related note20:10
r1chardj0n3s#topic swift ui-router update20:10
*** openstack changes topic to "swift ui-router update (Meeting topic: horizon)"20:10
r1chardj0n3swe have previously agreed that ui-router will be used where necessary for multi-level routing20:11
r1chardj0n3sI've got the first patch up that uses it in the Swift UI20:11
r1chardj0n3sIt's still a little WIP, but I'd like feedback now if possible20:11
r1chardj0n3s#link https://review.openstack.org/#/c/350523 has a big UI change, so feedback would be nice20:11
r1chardj0n3sin short, I nuked the containers sidebar and that's a pretty big change :-)20:12
r1chardj0n3sI'd like to know whether I need to try to revert that before continuing work on it20:12
* ducttape_ would like to see where containers go20:12
r1chardj0n3sducttape_: it's ok, to simplify things I just delete them all20:13
ducttape_rm -rf /openstack  is super simple20:13
r1chardj0n3s+2 +a20:13
ducttape_;)20:13
r1chardj0n3sso, feedback on the patch would be really appreciated :-)20:13
r1chardj0n3smoving on20:13
r1chardj0n3s#topic bootstrap update20:13
*** openstack changes topic to "bootstrap update (Meeting topic: horizon)"20:13
r1chardj0n3sWe're upgrading our xstatic angular-bootstrap this week!20:14
r1chardj0n3sThis is going to break EVERYTHING!!!20:14
r1chardj0n3swell, except mitaka and newton20:14
rdopierathe end is near20:14
rdopierarepent20:14
ediardodamn20:14
r1chardj0n3sbut master will break, as will Ocata's beta1 and beta2 releases20:14
r1chardj0n3swe have a plan for minimising the breakage20:14
r1chardj0n3sIn short, once https://review.openstack.org/#/c/409121/ merges the xstatic-angular-bootstrap 2.2.0.0 package will be released to pypi20:15
*** ociuhandu has joined #openstack-meeting-320:15
r1chardj0n3sin openstack land, a patch to upper-constraints.txt will be automatically generated by the release of that file, pushing the pin "XStatic-Angular-Bootstrap===0.11.0.8" to "XStatic-Angular-Bootstrap===2.2.0.0"20:16
r1chardj0n3s(yes, we're very, VERY out of date)20:16
r1chardj0n3sonce that pin changes, all the Ocata Horizons will break20:16
r1chardj0n3sso we have a patch we're going to try to release as simlutaneously as possible20:17
* ducttape_ thinks this is going to be very exciting in a terrible way20:17
tsufievOmg20:17
r1chardj0n3shttps://review.openstack.org/#/c/401245/20:17
tsufievShould it really make such a big step?20:17
r1chardj0n3sthat patch ain't perfect, but it does get Horizon working again20:17
r1chardj0n3stsufiev: the backward incompatible changes were introduced in angular-bootstrap 0.13 :-)20:18
r1chardj0n3swe've been out of date for a *very* long time20:18
ducttape_as long as we are cut from any nearby milestone branches, lets forge ahead20:18
robcresswellI'll take a look at the patch again if you like20:19
r1chardj0n3sas I said, stable mitaka and newton *should* be unaffected by this, since we've put in a lot of effort to ensure they remain pinned to 0.11.0.820:19
robcresswellI actually thought it fixed most things20:19
r1chardj0n3srobcresswell: I saw some styling artifacts, that's all20:19
*** hoppalm_ has joined #openstack-meeting-320:19
robcresswellOh I can do styling20:19
robcresswellDiana taught me20:19
r1chardj0n3s:-)20:19
r1chardj0n3sanyway, I don't want messing with that patch to delay it20:19
r1chardj0n3sonce this meeting is over I'll get on to hassling the release team about getting https://review.openstack.org/#/c/409121/ approved (I'm sure they have nothing better to do ;-)20:20
r1chardj0n3smaking https://review.openstack.org/#/c/401245/ depends-on the upper-constraints.txt patch that follows https://review.openstack.org/#/c/409121/ should minimise our breakage20:21
robcresswellSure20:21
r1chardj0n3s(especially if it's pre-approved and depends-on ...)20:21
robcresswell(I think I've solved microversions l support locally btw)20:21
robcresswell-l20:22
r1chardj0n3sOne more thing, then microversions ;-)20:22
rdopierainvalid option -l20:22
r1chardj0n3s#topic Integration tests are dead, long live integration tests!20:22
*** openstack changes topic to "Integration tests are dead, long live integration tests! (Meeting topic: horizon)"20:22
tsufievAmen20:22
*** hoppalm has quit IRC20:22
r1chardj0n3s#link https://review.openstack.org/#/c/410489/ is where they went away20:23
r1chardj0n3sour task now is to get some new tempest suite tests added in a nice, orderly, well-thought-out manner20:23
david-lylethat doesn't sound like us20:24
lcastell:)20:24
r1chardj0n3sI'm hoping to see a BP that we can use to create an initial small set of tempest additions at high level checking basic panel existence/functionality20:25
* r1chardj0n3s tags lcastell20:25
r1chardj0n3s:-)20:25
lcastello/20:25
* lcastell tags david-lyle20:25
r1chardj0n3sI'd like to see breadth of tests, rather than depth...20:25
r1chardj0n3s(it'd be super nice for the new suite to even check the angular panels ;-)20:26
* lcastell taking notes 20:26
david-lylelet's slow down on the unicorn farm20:26
*** hoppalm has joined #openstack-meeting-320:26
david-lylewe'll get some tests going :)20:26
r1chardj0n3sdammit, you said there were plenty of unicorns!20:27
robcresswellUnicorn farm?20:27
r1chardj0n3sspeaking of unicorns20:27
r1chardj0n3s#topic Microversions20:27
*** openstack changes topic to "Microversions (Meeting topic: horizon)"20:27
* r1chardj0n3s tags robcresswell20:27
david-lylehaha20:27
robcresswellSigh20:28
robcresswellSo we finished the blueprint for this, amongst much raging20:28
robcresswellI've got a patch that should go up tomorrow that does it in the least bad way possible I think20:28
*** hoppalm_ has quit IRC20:28
r1chardj0n3s(so confident, much microversions, wow)20:29
robcresswellAnd I've asked rhagarty to hold fire on his implementation to save us both time20:29
robcresswellSomeone else has also been implementing them in isolation and silence, but *shrug*20:29
robcresswellr1chardj0n3s: Ha, I'm quite confident in the patch, the implementation is only about 80 lines20:30
*** MeganR has quit IRC20:30
*** liangy has quit IRC20:30
*** Swami_ has quit IRC20:30
robcresswellI've used it for locked status on instances, and cinder consistency groups20:30
robcresswellAs examples :)20:31
robcresswellThat's all from me anyways20:31
rhagartyrobcresswell: thanks for driving20:31
r1chardj0n3s#link https://blueprints.launchpad.net/horizon/+spec/microversion-support is the BP, for reference20:31
*** hoppalm has quit IRC20:32
robcresswellThanks r1chardj0n3s20:32
r1chardj0n3sI look forward to your patch robcresswell!20:32
*** gouthamr has joined #openstack-meeting-320:33
r1chardj0n3srobcresswell: on the xstatic front, I believe there's some compatibility work needed for D3 as well?20:33
robcresswellr1chardj0n3s: Yeah, there is20:33
*** pcaruana has quit IRC20:33
r1chardj0n3sOK, I have someone to work on that then20:34
robcresswellOh good20:34
robcresswellI was about to say, kinda losing motivation on doing all our updates20:34
rdopierawe should rotate that position20:34
robcresswellWould be nice if someone else could drive a couple :)20:34
r1chardj0n3syep, I have helpers now though20:34
robcresswellAwesome20:35
*** ociuhandu has quit IRC20:35
*** sdake_ has joined #openstack-meeting-320:35
r1chardj0n3sthat's all I have for the agenda today - does anyone have anything they'd like to bring up?20:35
ying_zuorobcresswell: are you working on something for the instance locked status?20:35
ying_zuoI also have a patch for it.20:36
robcresswellying_zuo: Just adding proper microversion support :)20:36
robcresswellWell, consistent I should say20:36
ying_zuoI think that's what Cindy mentioned on the patch20:36
robcresswellIt won't change the functionality, but might require a rebase depending on who merges first20:36
*** ociuhandu has joined #openstack-meeting-320:37
ying_zuohttps://review.openstack.org/#/c/331874/20:37
*** hoppalm has joined #openstack-meeting-320:37
*** sdake has quit IRC20:37
ying_zuoI think my patch will need to rebase to yours?20:37
robcresswellAh right yes, the resulting work is in the blueprint r1chardj0n3s put up earlier20:37
robcresswellAnd my patch should go up tomorrow20:38
tsufievI was about to ask if anyone thinks horizon needs profiling of angular pages, https://review.openstack.org/#/c/358574/20:38
*** mariannelm has quit IRC20:38
ying_zuocool. thank you20:38
robcresswelltsufiev: That would be good20:38
robcresswellying_zuo: No problem20:38
r1chardj0n3stsufiev: yes! thank you for reminding me of that patch!20:38
*** matjazp has joined #openstack-meeting-320:38
tsufievBecause in terms of ui it may not provide a competitor to Chrome network profiler20:38
r1chardj0n3scores, I'd really like https://review.openstack.org/#/c/395873/ to not be in my sad patches list :-)20:39
tsufievAnd on the other hand, angular api calls are usually very fine-grained20:39
r1chardj0n3stsufiev: but it can go deeper than Chrome, yeah? it can profile the services as well?20:39
* rdopiera -1s it20:39
tsufievr1chardj0n3s: it can, but the UI as I said is inferior20:40
r1chardj0n3stsufiev: regardless of the inferiority of the UI, being able to see what's going on behind the server AJAX handler will be invaluable20:40
tsufievI mean, it needs to be taught how to show async calls20:40
r1chardj0n3srighto20:40
tsufievOk20:40
tsufievI'll try to improve it a bit then )20:41
r1chardj0n3sespecially if we can see *why* the nova API call is taking 30 seconds to respod - all Chrome can tell us is that it does :-)20:41
* r1chardj0n3s likes unicorns, please make more of them20:41
*** ociuhandu has quit IRC20:41
tsufievHmm, that would require support from the other part of profiling team20:42
r1chardj0n3sunicorns, dammit!!20:42
*** rtheis has quit IRC20:42
r1chardj0n3s;-)20:42
rdopierahttps://s-media-cache-ak0.pinimg.com/236x/1d/da/6b/1dda6b78a44783f963717043125e3da9.jpg20:43
* robcresswell is still confused20:43
robcresswellFat deranged unicorn?20:43
tsufievBloated unicorn )20:43
rdopierait has thick bones20:43
tsufievLike bloatware20:43
hurgleburgler\o/20:43
ducttape_husky20:44
tsufievhurgleburgler: were you summoned by a unicorn ;)?20:44
hurgleburglerApparently so20:44
hurgleburgler:-D20:44
hurgleburglera fat deranged one.20:44
robcresswellThat should be the Horizon logo20:44
r1chardj0n3sok, if there's no other business, I'll let y'all get back to your reviewing20:44
rdopieratoo late20:44
r1chardj0n3srobcresswell: omfg don't talk about the war20:45
robcresswellLol20:45
r1chardj0n3s#endmeeting20:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:45
openstackMeeting ended Wed Dec 14 20:45:25 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-12-14-20.00.html20:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-12-14-20.00.txt20:45
*** r1chardj0n3s has left #openstack-meeting-320:45
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-12-14-20.00.log.html20:45
*** rdopiera has left #openstack-meeting-320:45
*** tsufiev has left #openstack-meeting-320:45
*** robcresswell has left #openstack-meeting-320:45
*** ociuhandu has joined #openstack-meeting-320:52
*** ociuhandu has quit IRC20:56
*** dtp has joined #openstack-meeting-320:58
dansmith#startmeeting nova_cells21:00
openstackMeeting started Wed Dec 14 21:00:00 2016 UTC and is due to finish in 60 minutes.  The chair is dansmith. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova_cells)"21:00
openstackThe meeting name has been set to 'nova_cells'21:00
dansmithohai21:00
dtphi21:00
dansmithdtp: do you not stay on irc all the time? I went looking for you this morning and you weren't in -nova21:00
dtpi try to keep it closed.  i find #nova distracting21:00
dtpbut it's not a big deal.  i'll be on more21:01
melwitto/21:01
dansmithdtp: embrace the chaos21:01
dansmithokay,21:01
dansmith#topic test/bugs21:01
*** openstack changes topic to "test/bugs (Meeting topic: nova_cells)"21:01
dansmithwe had a bug this week when the tripleo people were trying to upgrade past the cell setup requirement21:02
*** ducttape_ has quit IRC21:02
dansmithI have a patch up to fix one of the major issues:21:02
dansmithhttps://review.openstack.org/#/c/409890/21:02
dansmithwhich was creating the cell0 map, then failing doing the host mapping,21:02
dansmithwhich means that if you ran it again it would never re-do the latter bit because it assumed the cell0 map meant it was done21:02
*** mriedem has joined #openstack-meeting-321:02
dansmiththat, and we have some documentation stuff we need to suck less at21:03
mriedemHI!21:03
dansmithany other bug/testing stuff?21:03
mriedemso, on docs21:03
mriedem:)21:03
mriedemi was thinking an arch diagram might be nice21:03
mriedemgiven mgagne's questions about where the api db lives in cells v121:03
dansmithI'm sure you were21:03
melwitt+1 to arch diagram21:04
dansmithso,21:04
dansmithin this fantasy I have about writing a blog post for this,21:04
dansmithI had planned a series of diagrams going from "normal nova" to "cellsv2"21:04
dansmithso you can see which parts get added, where, and why21:04
mriedemi'm sure you were21:04
melwittthat sounds super21:05
mriedem+1 on super21:05
*** tonytan4ever has quit IRC21:05
dansmithanything else on this subject?21:05
dansmith#topic open reviews21:06
mriedemnaw21:06
*** openstack changes topic to "open reviews (Meeting topic: nova_cells)"21:06
*** tonytan4ever has joined #openstack-meeting-321:06
dansmithmy megaseries has made some progress, but also grown more patches: https://review.openstack.org/#/c/367557/21:06
dansmithunit and functional tests pass for me on the top patch, however, which is somewhat mind boggling21:06
melwittthat's sweet21:07
dansmiththe bottom patch has a couple comments on an older PS that I could fix up21:07
dansmithbut otherwise, several at the bottom there should be good for reviews21:07
dansmithI noticed that melwitt pushed up a couple things for quotas21:08
dansmithmelwitt: it looked like those were just moving quotas to the api db.. did you decide against the counting plan?21:08
melwittyeah, I have WIP on them as they have no tests yet. but it would be nice to get a sanity check on where I'm going21:08
melwittno, counting is next and it's tied to a different spec21:08
dansmithI thought the point was to do the counting so we don't move them?21:08
melwittwe have to move limits and classes21:09
melwittI didn't move usages or reservations21:09
dansmithokay, well, I haven't looked so I should shut up I guess21:09
dansmithokay21:09
melwittso we have a minimal move needed to store quota limits and quota classes, even thought quota classes do nothing except handle the default quota21:10
dansmithyeah, I guess I forgot about having to move the settings separate from the records21:10
mriedemwe could take the opportunity to kill quota classes,21:10
melwittnext will be ripping out all the usages, reservations stuff and replacing it with counting21:10
mriedembut it's probably a bit late for that right now21:10
dansmithmriedem: yeah I was just wondering if we could just fake that or something21:10
mriedemi had a ML post in newton about removing quota classes...21:11
mriedembut it's all dropped out of my brain by now21:11
melwittyeah, that would involve a microversion on the API to take it out too right21:11
mriedemwell,21:11
mriedemi'm not sure about that21:11
mriedemthe api could still return the default quotas21:11
dansmithif it doesn't work, we just fake what we return right?21:11
melwittthe quota-class-sets that lets you create and update quota classes21:11
dansmithlike "oh yeah, there are totally some classes, and here they are"21:12
mriedemi'd have to go back and look at the ML thread21:12
dansmithoh, I didn't think you could actually create them21:12
mriedemi think some of the problem was some of that shit was already busted21:12
melwittoh yeah you can21:12
melwittwhich sucks21:12
*** egallen has joined #openstack-meeting-321:12
dansmithso you can create them but they don't work?21:12
mriedemhttp://lists.openstack.org/pipermail/openstack-dev/2016-July/099218.html21:13
mriedem" You can still create unique quota classes via the os-quota-class-sets  API (it does a create if the update operation fails), but as far as I  can tell you can't really use those in any meaningful way."21:13
melwittyeah, I read through that thread before moving them because it wasn't clear to me what it would take to remove them21:14
mriedem"I think we should also add a microversion to the API in Ocata to disable  the ability to create new quota classes, so that update is only update,  and a 404 for anything else."21:14
mriedemso...21:14
mriedemwe could just make update an update for default21:14
mriedemand that's it21:14
mriedeman update on a thing that doesn't exist is a 40021:14
mriedemor 40421:14
mriedemrather than update or create21:15
melwittthat means we still have to move them I guess, if update is possible? if someone already created some other classes in the past? or does that not matter because no class other than default does anything?21:15
dansmithor just not move those21:15
dansmithso that they all become 404 :)21:15
*** tonytan4ever has quit IRC21:15
dansmithif there's no way to really use this, are we just being silly by maintaining compatibility?21:15
*** Swami has joined #openstack-meeting-321:15
melwittwe have to move them if they do something, I just don't understand yet whether they do anything. the non default ones if someone created some21:15
dansmithcompat is all well and good until you orchestrate a giant move of nothing from one database to another to ensure that a broken thing remains broken :/21:16
*** ying_zuo has quit IRC21:16
melwittyeah, agreed. if existing non default quota classes don't do anything, then we won't have to move them21:16
mriedemVek did provide the original concept http://lists.openstack.org/pipermail/openstack-dev/2016-July/099270.html21:16
mriedemyou create a class with more or less quota, and apply that to a tenant21:16
dansmithso vek said he didn't care if it went away, and sdague said he'd be okay dropping it21:17
mriedemin practice i don't know of anyone that uses it21:17
dansmithmriedem: but I thought it doesn't actually work for anything but default21:17
dansmithare you saying it does ?21:17
mriedemidk, would have to test it out21:17
mriedemlike,21:18
mriedemmaybe i can change global default quota to 1 instance per tenant,21:18
*** julim_ has quit IRC21:18
mriedembut then create a custom quota class that allows 2 instances per tenant, and assign that to another tenant, and see if i can create >1 instance on it21:18
melwittyeah. that would probably be a lot easier than trying to figure out from the code whether non default classes work21:18
melwittbecause it's awesomely confusing21:19
mriedemso i'll take the todo to see you can actually use this today21:19
dansmithokay, so mriedem you're going to do that?21:19
dansmithcool21:19
mriedemi've got a fresh desvstack21:19
mriedembut yeah the quota classes stuff plumbed throughout the code makes everything harder to follow21:19
dansmithyeah21:19
dansmithokay, moving on21:20
mriedem#action mriedem to see if custom quota classes actually work21:20
dansmithdtp: did you push up a review?21:20
dtpnot yet21:20
dtpbut i have questions21:20
dansmithdtp: shoot21:20
dtphttps://github.com/openstack/nova/blob/master/nova/consoleauth/rpcapi.py#L9221:20
dtpif i understand what i'm doing here -21:20
dtpi need to get the real data behind that token from memcache21:21
dtpso that i can get the instance_uuid21:21
dtpso is memcache somehow shared across all the cells?21:21
dtpotherwise, if we're running a separate cache in each cell21:22
dtpthen i'll need to get to the cache to pull out of it, but i need the instance uuid to get to it21:22
melwittyeah, I was thinking the memcache is global but I haven't actually used the tokens before21:22
dansmithwell,21:22
dansmithit'd be good if that didn't matter21:23
dansmithso the problem is that we don't have the instance_uuid in the url for the console?21:23
dtpthat is one idea.  if i could get instance uuid passed, that would make things easier21:23
dtpor perhaps the only idea21:24
dansmithdidn't we discuss adding the instance to the url already?21:24
melwittargh, I had thought that was available on the client side but it isn't21:24
dansmithperhaps for a different problem21:24
dansmithyeah it's not21:24
melwittwhat do you mean by add it to the url?21:24
dansmiththe console url is something like /console/<token> or something right?21:25
dtpyes21:25
dansmithso if it was /console/<instanceuuid>/<token>21:25
dansmiththen we'd have both21:25
*** VW has quit IRC21:25
melwittlike the rest api call you mean? or something else21:25
dansmiththat'd be hella better than having to talk to memcache from this side21:25
bauzasholy snap21:26
dtpand since we generate console urls, we can do this?21:26
bauzasjust missed the beginning of the meeting21:26
dansmithmelwitt: well, the url you make the console call on, which is in the instance I think21:26
dansmithdtp: I would think we could21:26
melwittyeah, I didn't intend on talking to memcache on the client side. I just didn't realize I was looking at the server side or something at the time21:26
dansmithoh yeah,21:27
dansmithI think it's easy21:27
dansmithit's ?token= even21:27
dansmithso just add instance_uuid in ther21:27
melwitteasy == GOOD21:27
dansmithsec21:27
dansmithhttps://github.com/openstack/nova/blob/master/nova/compute/manager.py#L4546-L454821:27
dansmithnow, here's the rub21:28
dansmiththat is done on the compute side,21:28
*** ianychoi has quit IRC21:28
dansmithwhich would make the api stop working until all computes get upgraded21:28
dansmithso what might be even better is to have the api-side of that call tack on the instance uuid before returning what the compute returned,21:28
dansmithwhich would fix it before computes are upgraded21:28
dansmithso here: https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/remote_consoles.py#L67-L6721:29
dansmithyou could tack on the instance uuid21:29
melwittah, cool21:29
dansmithdtp: you will want to sync up with sdague on this I think21:29
dansmithbut I think that's probably okay,21:29
dansmithand I think he might've been in a convo about this for a different thing a while ago21:29
melwittdo we need to worry about existing urls that don't have instance uuid?21:29
dansmithdtp: if he seems receptive, tell him "dansmith sent me"21:29
dansmithdtp: and if not, tell him it's all youridea21:30
dtplol21:30
dtpi'm still processing what you have said, but don't let me hold you up21:30
dansmithmelwitt: it would mean anyone that grabbed a url before an upgrade wouldn't work, but they would just re-ask and get an updated one21:30
dansmithmelwitt: so I don't think it's too bad21:30
melwittokay, cool21:31
dtphow is sdague involved?21:31
dansmithdtp: so, this is turning into a little more meaty thing, but still not to bad I think21:31
dansmithdtp: he says "no" to a lot of API stuff21:31
*** rossella_s has quit IRC21:31
dansmithdtp: if we can catch him in the next couple days I'll be glad to be there for that convo21:32
dansmithdtp: if not, melwitt can surely back you up21:32
dansmithsdague likes melwitt a lot more than he likes me anyway, so that's probably a good thing21:32
*** rossella_s has joined #openstack-meeting-321:32
melwitthah21:33
melwittand yes, I can help talk to him next week if we can't catch him this week21:33
dansmithdtp: okay, so have we jammed your brain full for the moment? definitely ask this kinda stuff sooner on irc if anything else comes up21:33
mriedemmelwitt: are you around next week?21:33
dtpyes, head is full.  i would have but i have been delayed21:34
mriedemdan is out after friday21:34
melwittmriedem: yep21:34
melwittI think I have next friday off as a company holiday21:34
melwittso I'll be around monday - thursday21:35
mriedemalright21:35
dansmithokay so, speaking of that21:35
dansmithdo we need to have a cells meeting for the next two weeks?21:35
dansmithif so, ya'll'er on your own21:35
bauzashard21:36
mriedemdansmith: probably not21:37
dansmithsoft?21:37
mriedemlimp21:37
dansmithokay, so unless someone speaks up I shall send a mail to the list about it21:37
mriedemi probably need to talk to jay about his involvement in the upcoming pagan holiday21:37
dtpwhen is this work due?21:37
dansmithdtp: heh, are you a student?21:37
mriedemdtp: feature freeze is january 26th21:38
dtp*studen of nova cells v2*21:38
*** VW has joined #openstack-meeting-321:38
dansmithbah dum dum21:38
dtpok21:38
*** VW has quit IRC21:38
dansmithsince we have already...21:38
dansmith#topic open discussion21:38
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"21:38
dansmithanything else?21:38
*** VW has joined #openstack-meeting-321:39
dansmithokay then21:40
dansmithdtp: don't be a stranger, ask in -nova and ye shall receive :)21:40
dansmith#endmeeting21:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:40
openstackMeeting ended Wed Dec 14 21:40:50 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:40
*** mriedem has left #openstack-meeting-321:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-12-14-21.00.html21:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-12-14-21.00.txt21:40
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-12-14-21.00.log.html21:40
*** egallen has quit IRC21:45
*** sdake_ has quit IRC21:46
*** TravT has joined #openstack-meeting-321:48
*** cleong has quit IRC22:08
*** lblanchard has quit IRC22:10
*** rossella_s has quit IRC22:11
*** rossella_s has joined #openstack-meeting-322:12
*** liangy has joined #openstack-meeting-322:28
*** VW has quit IRC22:31
*** alexismonville has quit IRC22:38
*** baoli has quit IRC22:44
*** gouthamr has quit IRC22:45
*** marst has quit IRC22:45
*** Swami has quit IRC22:50
*** gouthamr has joined #openstack-meeting-322:57
*** sdake has joined #openstack-meeting-323:02
*** rbak has quit IRC23:06
*** sdake has quit IRC23:08
*** VW has joined #openstack-meeting-323:10
*** s3wong has joined #openstack-meeting-323:11
*** mtanino has quit IRC23:15
*** mtanino has joined #openstack-meeting-323:15
*** sdake has joined #openstack-meeting-323:15
*** jschwarz has quit IRC23:16
*** sdake has quit IRC23:16
*** jjung has quit IRC23:18
*** yamahata_ has quit IRC23:21
*** jschwarz has joined #openstack-meeting-323:21
*** iyamahat has quit IRC23:23
*** ianychoi has joined #openstack-meeting-323:25
*** VW has quit IRC23:25
*** VW has joined #openstack-meeting-323:27
*** sdake has joined #openstack-meeting-323:28
*** VW has quit IRC23:28
*** sdague has quit IRC23:31
*** sdake_ has joined #openstack-meeting-323:36
*** sdake has quit IRC23:37
*** baoli has joined #openstack-meeting-323:46
*** Swami has joined #openstack-meeting-323:56
*** donghao has quit IRC23:59

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