Wednesday, 2017-11-29

*** yamamoto has joined #openstack-meeting-300:12
*** hongbin has quit IRC00:13
*** slaweq has joined #openstack-meeting-300:13
*** slaweq has quit IRC00:18
*** yamamoto has quit IRC00:31
*** bobh has joined #openstack-meeting-300:32
*** salv-orl_ has quit IRC00:38
*** salv-orlando has joined #openstack-meeting-300:38
*** VW has joined #openstack-meeting-300:39
*** salv-orlando has quit IRC00:43
*** mguiney has quit IRC00:43
*** sdague has quit IRC00:44
*** mguiney has joined #openstack-meeting-300:44
*** chyka has quit IRC00:47
*** vishwanathj has joined #openstack-meeting-300:57
*** shuyingya has joined #openstack-meeting-301:10
*** shuyingya has quit IRC01:15
*** yamamoto has joined #openstack-meeting-301:20
*** Swami has quit IRC01:22
*** shuyingya has joined #openstack-meeting-301:36
*** salv-orlando has joined #openstack-meeting-301:39
*** shuyingya has quit IRC01:41
*** gmann_afk is now known as gmann01:41
*** salv-orlando has quit IRC01:44
*** shuyingya has joined #openstack-meeting-301:48
*** shuyingy_ has joined #openstack-meeting-301:49
*** shuyingya has quit IRC01:53
*** yamamoto has quit IRC02:07
*** shu-mutou-AWAY has quit IRC02:09
*** mguiney has quit IRC02:14
*** mguiney has joined #openstack-meeting-302:14
*** chyka has joined #openstack-meeting-302:17
*** chyka has quit IRC02:21
*** yamamoto has joined #openstack-meeting-302:23
*** salv-orlando has joined #openstack-meeting-302:40
*** bobh has quit IRC02:42
*** salv-orlando has quit IRC02:45
*** iyamahat has quit IRC03:00
*** yamahata has quit IRC03:02
*** ywat has joined #openstack-meeting-303:11
*** yamamoto has quit IRC03:18
*** coolsvap has joined #openstack-meeting-303:33
*** kei-ichi has quit IRC03:56
*** kei-ichi has joined #openstack-meeting-303:57
*** VW_ has joined #openstack-meeting-304:00
*** VW has quit IRC04:00
*** VW_ has quit IRC04:02
*** VW has joined #openstack-meeting-304:02
*** slaweq has joined #openstack-meeting-304:15
*** d0ugal has quit IRC04:18
*** slaweq has quit IRC04:19
*** d0ugal has joined #openstack-meeting-304:25
*** bobh has joined #openstack-meeting-304:25
*** TuanLA has joined #openstack-meeting-304:28
*** bobh has quit IRC04:29
*** shu-mutou has joined #openstack-meeting-304:29
*** markvoelker has quit IRC04:30
*** yamamoto has joined #openstack-meeting-304:36
*** salv-orlando has joined #openstack-meeting-304:42
*** gouthamr has quit IRC04:43
*** pgadiya has joined #openstack-meeting-304:43
*** pgadiya has quit IRC04:45
*** yamamoto has quit IRC04:46
*** salv-orlando has quit IRC04:46
*** kei-ichi has quit IRC05:03
*** kei-ichi has joined #openstack-meeting-305:05
*** yamamoto has joined #openstack-meeting-305:09
*** dklyle has quit IRC05:15
*** reedip has quit IRC05:17
*** VW_ has joined #openstack-meeting-305:24
*** VW has quit IRC05:24
*** markvoelker has joined #openstack-meeting-305:30
*** yamamoto has quit IRC05:31
*** VW_ has quit IRC05:33
*** VW has joined #openstack-meeting-305:33
*** chyka has joined #openstack-meeting-305:36
*** VW has quit IRC05:38
*** chyka has quit IRC05:41
*** yamamoto has joined #openstack-meeting-305:43
*** gouthamr has joined #openstack-meeting-305:46
*** yamamoto has quit IRC05:56
*** marios has joined #openstack-meeting-305:58
*** yamamoto has joined #openstack-meeting-306:01
*** yamamoto has quit IRC06:01
*** gouthamr has quit IRC06:04
*** cshastri has joined #openstack-meeting-306:06
*** Kvisle has quit IRC06:06
*** Kvisle has joined #openstack-meeting-306:07
*** yamahata has joined #openstack-meeting-306:09
*** alex_xu has quit IRC06:10
*** alex_xu has joined #openstack-meeting-306:11
*** slaweq has joined #openstack-meeting-306:17
*** shuyingya has joined #openstack-meeting-306:21
*** shuying__ has joined #openstack-meeting-306:22
*** shuyingy_ has quit IRC06:24
*** shuyingya has quit IRC06:25
*** salv-orlando has joined #openstack-meeting-306:25
*** iyamahat has joined #openstack-meeting-306:28
*** marios has quit IRC06:31
*** marios has joined #openstack-meeting-306:32
*** kei-ichi has quit IRC06:34
*** slaweq has quit IRC06:35
*** kei-ichi has joined #openstack-meeting-306:35
*** slaweq has joined #openstack-meeting-306:35
*** lpetrut has joined #openstack-meeting-306:38
*** shuyingya has joined #openstack-meeting-306:39
*** shuyingya has joined #openstack-meeting-306:39
*** slaweq has quit IRC06:40
*** shuying__ has quit IRC06:43
*** yamamoto has joined #openstack-meeting-306:56
*** yamamoto has quit IRC07:01
*** anilvenkata has joined #openstack-meeting-307:04
*** lpetrut has quit IRC07:37
*** mguiney has quit IRC07:45
*** mguiney has joined #openstack-meeting-307:47
*** lpetrut has joined #openstack-meeting-307:53
*** lpetrut has quit IRC07:54
*** reedip has joined #openstack-meeting-308:01
*** stendulker has joined #openstack-meeting-308:04
*** pcaruana has joined #openstack-meeting-308:04
*** ccamacho has joined #openstack-meeting-308:12
*** rmart04 has joined #openstack-meeting-308:21
*** rossella_s has quit IRC08:23
*** e0ne has joined #openstack-meeting-308:44
*** liuyulong has joined #openstack-meeting-308:56
*** fouadben has joined #openstack-meeting-309:02
*** MarkBaker has joined #openstack-meeting-309:18
*** etingof has quit IRC09:29
*** MarkBaker has quit IRC09:30
*** MarkBaker has joined #openstack-meeting-309:30
*** gcb has joined #openstack-meeting-309:39
*** gmann is now known as gmann_afk09:39
*** yamamoto has joined #openstack-meeting-309:41
*** etingof has joined #openstack-meeting-309:49
*** iyamahat has quit IRC09:52
*** slaweq has joined #openstack-meeting-309:55
*** slaweq has quit IRC10:00
*** TuanLA has quit IRC10:05
*** yamahata has quit IRC10:13
*** MarkBaker_ has joined #openstack-meeting-310:15
*** MarkBaker has quit IRC10:17
*** MarkBaker_ has quit IRC10:20
*** shu-mutou is now known as shu-mutou-AWAY10:21
*** sambetts|afk is now known as sambetts10:26
*** donghao has joined #openstack-meeting-310:55
*** gcb has quit IRC11:05
*** yamamoto has quit IRC11:06
*** tellesnobrega has quit IRC11:06
*** slaweq has joined #openstack-meeting-311:10
*** yamamoto has joined #openstack-meeting-311:10
*** haint_ has joined #openstack-meeting-311:16
*** slaweq has quit IRC11:19
*** slaweq has joined #openstack-meeting-311:19
*** MarkBaker_ has joined #openstack-meeting-311:20
*** haint has quit IRC11:21
*** yamamoto has quit IRC11:24
*** slaweq has quit IRC11:24
*** stendulker_ has joined #openstack-meeting-311:25
*** stendulker_ has quit IRC11:26
*** stendulker_ has joined #openstack-meeting-311:27
*** sdague has joined #openstack-meeting-311:27
*** stendulker has quit IRC11:28
*** stendulker_ has quit IRC11:32
*** shuyingy_ has joined #openstack-meeting-311:52
*** tellesnobrega has joined #openstack-meeting-311:53
*** shuyingya has quit IRC11:55
*** chyka has joined #openstack-meeting-311:58
*** chyka has quit IRC12:02
*** slaweq has joined #openstack-meeting-312:10
*** bobh has joined #openstack-meeting-312:20
*** slaweq has quit IRC12:21
*** yamamoto has joined #openstack-meeting-312:24
*** yamamoto has quit IRC12:31
*** yamamoto has joined #openstack-meeting-312:34
*** raildo has joined #openstack-meeting-312:39
*** slaweq has joined #openstack-meeting-312:39
*** slaweq has quit IRC12:44
*** psachin has joined #openstack-meeting-312:48
*** bobh has quit IRC12:50
*** bobh has joined #openstack-meeting-312:51
*** ansmith has quit IRC12:57
*** yamamoto has quit IRC13:04
*** yamamoto has joined #openstack-meeting-313:08
*** yamamoto has quit IRC13:08
*** yamamoto has joined #openstack-meeting-313:09
*** yamamoto has quit IRC13:09
*** bobh has quit IRC13:11
*** yamamoto has joined #openstack-meeting-313:14
*** slaweq has joined #openstack-meeting-313:15
*** yamamoto has quit IRC13:19
*** markvoelker has quit IRC13:19
*** markvoelker has joined #openstack-meeting-313:19
*** liuyulong has quit IRC13:21
*** haleyb has quit IRC13:35
*** zhurong has joined #openstack-meeting-313:38
*** shuyingy_ has quit IRC13:39
*** haleyb has joined #openstack-meeting-313:39
*** shuyingya has joined #openstack-meeting-313:40
*** openstack has joined #openstack-meeting-313:45
*** ChanServ sets mode: +o openstack13:45
*** lyan has joined #openstack-meeting-313:47
*** lhx_ has joined #openstack-meeting-313:54
*** zhurong has quit IRC13:56
*** ansmith has joined #openstack-meeting-313:56
*** zhurong has joined #openstack-meeting-313:58
*** yamamoto has joined #openstack-meeting-314:14
*** yamamoto has quit IRC14:15
*** yamamoto has joined #openstack-meeting-314:15
*** yamamoto has quit IRC14:15
*** slaweq has quit IRC14:17
*** sgrasley1 has quit IRC14:17
*** tosky has joined #openstack-meeting-314:23
*** donghao has quit IRC14:23
*** psachin has quit IRC14:28
*** yamamoto has joined #openstack-meeting-314:36
*** cshastri has quit IRC14:37
*** tellesnobrega has quit IRC14:38
*** hongbin has joined #openstack-meeting-314:40
*** yamamoto has quit IRC14:41
*** sc has joined #openstack-meeting-314:42
*** zhurong has quit IRC14:46
*** zhurong has joined #openstack-meeting-314:46
*** openstack has quit IRC14:46
*** openstack has joined #openstack-meeting-314:51
*** ChanServ sets mode: +o openstack14:51
*** skarlsson has joined #openstack-meeting-314:55
*** skarlsson has quit IRC14:56
*** witek has joined #openstack-meeting-314:56
*** d0ugal has quit IRC14:56
*** skarlsson has joined #openstack-meeting-314:58
*** cbellucci has joined #openstack-meeting-314:59
*** joadavis has joined #openstack-meeting-314:59
witek#startmeeting monasca15:00
openstackMeeting started Wed Nov 29 15:00:30 2017 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
scyo15:00
jgrHello15:00
fouadbenhi15:00
witekhello15:00
cbellucciHello15:00
*** Neptu has joined #openstack-meeting-315:00
tobiajohi15:00
joadavishiya15:00
witekjust two items on the agenda today15:01
*** haruki has joined #openstack-meeting-315:01
witekfeel free to add15:01
witek#topic monasca-agent detection15:01
*** openstack changes topic to "monasca-agent detection (Meeting topic: monasca)"15:01
Neptuhej15:01
*** salv-orl_ has joined #openstack-meeting-315:02
*** jgu has joined #openstack-meeting-315:02
witekhi Neptu15:02
witekis it your topic?15:02
Neptuno not really15:02
witekTobias reported the bug in detection plugin15:03
*** salv-orlando has quit IRC15:03
*** sgrasley1 has joined #openstack-meeting-315:03
Neptuim working now more into k8s15:03
tobiajoit was me that wanted to address the fact that monasca-setup often crashes when it uses oslo_config15:03
witektrying to parse configuration using oslo.config15:03
tobiajolink to reported issue: https://storyboard.openstack.org/#!/story/200130315:03
witekI had a look at this before the meeting15:03
*** d0ugal has joined #openstack-meeting-315:04
witekit looks to me, that parsing the config file is imlemented not robust enough, as you noted15:04
tobiajowhat did you find. anyone here that was involved implementing the usage of oslo.config?15:04
witekthe only two build-in options for oslo.config are  config_file and config_dir15:05
witekonly these should be accepted from the cmdline15:06
*** anilvenkata has quit IRC15:06
*** marst has joined #openstack-meeting-315:06
*** zhipeng has joined #openstack-meeting-315:06
witekso the bug is in monasca_setup.detection.utils.load_oslo_configuration15:06
*** yamamoto has joined #openstack-meeting-315:06
tobiajowhat solution do you see?15:06
witekchange the code around this line https://github.com/openstack/monasca-agent/blob/stable/pike/monasca_setup/detection/utils.py#L18615:07
*** coolsvap has quit IRC15:07
witekto accept only buil-in options15:07
*** yamamoto has quit IRC15:07
witekhttps://docs.openstack.org/oslo.config/latest/reference/builtins.html15:07
*** yamamoto has joined #openstack-meeting-315:08
*** yamamoto has quit IRC15:08
witekwhat do you think?15:08
*** nseyvet has joined #openstack-meeting-315:08
witekwe can continue the discussion in the story15:09
tobiajoif only config_file and config_dir should be accepted, it easy to patch. but what was the reason behind impl. usage of oslo.config here?15:09
tobiajoi don't see the reason behind this added complexity15:10
*** johnwhitlow[m] has joined #openstack-meeting-315:10
witekto have generic way of getting information from configuration files15:10
witekevery deployment can have them in different locations15:11
tobiajomakes sense15:12
*** psachin has joined #openstack-meeting-315:13
tobiajoif non one else have any input it is ok for me to continue on to the next topic15:13
*** bobh has joined #openstack-meeting-315:14
witekbtw. only two plugins use it at the moment, as far as I can see15:14
witekand there is an epic story for this:15:14
*** Yavor_OP5 has joined #openstack-meeting-315:14
witekhttps://storyboard.openstack.org/#!/story/200099915:14
witek#topic PTG in Dublin15:15
*** openstack changes topic to "PTG in Dublin (Meeting topic: monasca)"15:15
witekOpenStack Foundation has officially announced the next Project Teams Gathering15:16
witekit will be held in Dublin,  February 26 - March 2, 201815:16
witekI've been asked if Monasca will attend the Gathering15:17
*** d0ugal_ has joined #openstack-meeting-315:17
scI'll attend ;-)15:17
*** anilvenkata has joined #openstack-meeting-315:17
jguI am interested but will see if there is travel budget15:17
witekyes, you're half Irish :)15:18
*** yamahata has joined #openstack-meeting-315:18
scwitek: hahaha15:18
*** iyamahat has joined #openstack-meeting-315:18
witekI wanted to generally ask, if you think it's a good idea to meet in person15:18
witekor you prefer a video conference15:19
Yavor_OP5I think it would be beneficial15:19
witekfor people having budget problem, there is Travel Support Program15:19
*** d0ugal has quit IRC15:20
witekthe details are described on the website15:20
witekhttps://www.openstack.org/ptg/15:20
scwitek: I prefer meeting in person and this time I hope to get funds for the short travel15:20
witekyes, I also prefer meeting in person, but having representation of all parties is also important15:21
*** gouthamr has joined #openstack-meeting-315:22
witekso, I have set up again a Google Form to collect your opinions15:22
scgood15:22
jguwitek: thanks for the link. It's int'l travel for me so we'll see :-). I prefer to meet in person since it's quite a while. But I imagine we may alway need a conference line for those who couldn't travel.15:23
witekyes, that's an option too15:23
witekalthough it's not the same15:24
jguagreed :-)15:25
witekI have to give the answer if Monasca is attending next week15:25
witekso please fill in the form, and we'll update next week15:26
*** zhipeng has quit IRC15:27
witek#topic Cassandra update15:27
*** openstack changes topic to "Cassandra update (Meeting topic: monasca)"15:27
jguthat's me. Just wanted to give a quick update that cassadra now has passed the new zuul gates with cassandra as tsdb.15:27
witekgreat news!15:27
scWOW15:28
nseyvetcongrats!15:28
witek'Depends-On:' tags seem to work :)15:28
joadavis+115:28
jguyeah, thx all for the help :-)15:28
witekI think we can finally get someone for review this week15:29
*** zhipeng has joined #openstack-meeting-315:29
sclooks strange but I'm quite free next days so I can go to my backlog of reviews15:29
jguthat'd be great. The python persister impl now also has the smart batching feature that has potential to get similar performance as Java. We will test that out once Java performance testing is finished (only one test environment)15:30
witeksc: would be great15:30
jgusc and witek: thanks in advance!15:30
witekare you updating the performance results somewhere?15:30
tobiajocongrats :)! good work15:31
jguwhere would be a good place to put the ifnal performanc enumber?15:31
jgutobiajo: thanks15:31
witekyou had that etherpad, I think that's OK for now15:32
witekhttps://etherpad.openstack.org/p/cassandra_monasca15:32
jgusounds good. We'll refresh that etherpad and reposted the link in the IRC once it's done15:33
*** anilvenkata has quit IRC15:33
witekthanks15:33
tobiajoa little off topic: would performance have it place on docs.openstack.org/monasca-api ?15:33
*** georgk has joined #openstack-meeting-315:33
witekcould be, but there are more basic things missing there right now :(15:34
*** d0ugal has joined #openstack-meeting-315:34
witeklike installation, configuration, usage15:35
witekdo we have anything else for today?15:36
jgushould we have a wiki for performance and tuning?15:37
*** d0ugal_ has quit IRC15:37
witekyes, wiki would probably be better than d.o.o15:37
tobiajodoes other OS projects have that?15:37
*** psachin has quit IRC15:37
witektobiajo: I don't know, have to check15:38
jguwhat is d.o.o?15:38
witekdocs.openstack.org15:38
jgugot it15:38
witekbtw. the wiki page needs a clean-up15:38
witekand also, do we want to maintain both?15:39
scsorry, I don't understand your question?15:39
witekdo we want to maintain wiki and docs.openstack.org?15:40
tobiajod.o.o and wiki?15:40
jguI don't find Monasca on the https://docs.openstack.org/pike/projects.html15:40
witekor should we rather deprecate wiki, and use d.o.o only15:40
*** VW has joined #openstack-meeting-315:40
*** VW has quit IRC15:40
scwitek: I think that users are more likly going to docs.o.o15:40
tobiajoi don't see any reason to have both15:41
*** VW has joined #openstack-meeting-315:41
witekjgu: I can add it, there is just not much info there till now15:41
jguI agree with sc. d.o.o is more end user facing15:41
scwiki is for tips and tricks, user provided documentation (that deployment we forgot)...15:42
witekI also would prefer to have d.o.o in good shape and remove most of information from wiki15:43
*** caboucha has joined #openstack-meeting-315:44
witekIs there anyone interested on working on documentation?15:45
*** rmart04 has quit IRC15:45
witekI could start with defining the tasks15:45
*** Sukhdev has joined #openstack-meeting-315:47
witekso coming back to the origin question, yes we could probably add performance section as well15:47
jgusure. I am generally no good/help at documentation but I'll check out the task list you are going to create and see if I can help some.15:48
scwriting docs is a nighmare, we have to have docs but ... could we autogenerated from docstrigns? ;-)15:48
witekfor api-ref possibly yes15:48
witekthere is also that change for python client:15:49
witekhttps://review.openstack.org/#/c/511341/15:50
witekclick on build-openstack-sphinx-docs job output to see the rendered docs15:50
*** sgrasley2 has joined #openstack-meeting-315:51
witekif there is nothing else, I think we can close the meeting15:52
witekplease think about PTG and the google form15:53
joadavisI'll add a quick status on monasca-ceilometer.  After the Zuul v3 update we found the gates failed even on some simple changes.  Disabled the requirements-check gate (was tripping on a git+https reference for pulling in ceilometer) and now I'm working on bringing the code up to date with Ceilometer Pike. The intent is to get in sync before submitting the publisher to Ceilometer, an action item that came out of the Monasca15:53
joadaviseens mid-cycle.15:53
witekbye, see you next week15:53
*** sgrasley1 has quit IRC15:54
*** sgrasley2 is now known as sgrasley115:54
witekjoadavis: ok, thanks15:54
witekso, are zuul jobs working now?15:54
witekfor monasca-ceilometer?15:55
joadavisThere is a pending commit that needs a +2, but that gets around the issue. https://review.openstack.org/#/c/518414/  And a change was put in the upstream project config that made it possible.15:56
witekok, adding myself to review15:57
joadavisThanks. :)15:57
witekthank you everyone15:57
witekbye15:58
harukithank you15:58
joadavisbye15:58
cbelluccibye15:58
*** haruki has quit IRC15:58
tobiajobye15:58
*** cbellucci has quit IRC15:58
witek#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Wed Nov 29 15:58:27 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-11-29-15.00.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-11-29-15.00.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-11-29-15.00.log.html15:58
*** joadavis has left #openstack-meeting-315:58
*** fouadben has left #openstack-meeting-315:58
tobiajowitek: thanks for the help15:58
witektobiajo: sorry, it took that long :)15:59
jguthanks, b ye15:59
*** e0ne has quit IRC15:59
*** iyamahat has quit IRC16:01
eglute#startmeeting interopwg16:01
openstackMeeting started Wed Nov 29 16:01:48 2017 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: interopwg)"16:01
openstackThe meeting name has been set to 'interopwg'16:01
markvoelkero/16:01
dimso/16:02
eglute#chair markvoelker hogepodge16:02
openstackCurrent chairs: eglute hogepodge markvoelker16:02
eglute#topic agenda16:02
*** openstack changes topic to "agenda (Meeting topic: interopwg)"16:02
egluteHello everyone!16:02
georgkhi16:02
egluteHere is today's agenda: #link https://etherpad.openstack.org/p/InteropVertigo.2116:02
hogepodgehi16:02
mguineyo/16:03
*** psachin has joined #openstack-meeting-316:03
egluteI will be traveling next week, Dec 6-13, so I won't be able to make next two meetings. I hope markvoelker and hogepodge will be able to cover, as it turns out i will be traveling during meeting time16:03
*** zhipeng has quit IRC16:03
markvoelkerI should be here.16:04
eglutethanks markvoelker16:04
eglute#topic cycle name16:04
hogepodgeI'll be traveling next week, and unavailable on Wednesday.16:04
*** openstack changes topic to "cycle name (Meeting topic: interopwg)"16:04
hogepodgeI'll also be on vacation for the remainder of the month of December, so again unavailable.16:04
egluteEveryone, please enter your suggestion for new cycle name and vote for your top choice16:04
eglutewe will select the name at the end of this meeting16:04
eglute#topic Vertical Program Update16:05
*** openstack changes topic to "Vertical Program Update (Meeting topic: interopwg)"16:05
*** iyamahat has joined #openstack-meeting-316:05
eglute#link https://review.openstack.org/#/c/519732/16:05
eglutenot sure if georgk is around16:05
georgkI am16:05
eglutethank you georgk for all the patches16:05
eglutethey look good to me, but i am not NFV expert16:06
georgkso, this patchset now includes initial scoring for the trunk port feature + the candidates from the etherpad16:06
egluteso we really need everyone else to look at this as well16:06
eglutethank you georgk16:06
georgkI also added a few more candidates16:06
eglutethey look great16:06
egluteif everyone else will review them, we can merge it soon16:07
georgkyes, feedback is very welcome16:07
eglutegeorgk you added some notes to etherpad- does that mean you will score additional capabilities?16:07
*** psachin has quit IRC16:08
georgkyes, I wanted to move on to other capabilities as well16:08
*** yamamoto has joined #openstack-meeting-316:08
georgkI looked at networking-bgp, but there are some issues with the tempest tests16:08
*** coolsvap has joined #openstack-meeting-316:09
egluteok, does that mean you won't be adding those?16:09
georgkquestion is if I should add this to the current patch or to a separate16:09
*** psachin has joined #openstack-meeting-316:10
georgkI prefer a separate one - just to keep things apart16:10
eglutei think that will work16:10
georgkor rather clearly separated16:10
eglutedo you need us to merge this one first?16:10
*** Yavor_OP5 has quit IRC16:10
markvoelkerLEt's do separate.  Some of the others are going to be more controversial I think (like bgpvpn)16:10
*** tellesnobrega has joined #openstack-meeting-316:10
georgkwell, please review it of course, I can create a dependent patch16:10
mguineyo716:11
eglutesounds good georgk16:11
egluteo816:11
*** sc has left #openstack-meeting-316:11
eglutegeorgk also you have a comment about scenario tests16:11
georgkyes. what is the policy here? do we typically only include API tests16:12
eglutewe dont have any capabilities right now that use scenario tests16:12
georgkthe background is that the API tests of the networkiing-bgp projects do not cover simple things like listing or showing stuff16:13
markvoelkerFor the vertical programs I think some scenario tests may be appropriate.16:13
georgkhowwver, the scenario tests are more evolved16:13
eglutei am ok with including scenario tests for vertical programs16:14
georgkI reached out to the project to discuss if they can close the test gap16:14
georgkno reply yet :-)16:14
markvoelkerThat is to say: I would not exclude scenario tests from consideration.  The main difficulty is that they often test multiple capabilities, so you have to be a little careful...16:14
eglutemarkvoelker that would be my main concern as well16:14
markvoelkerE.g. if it tests something that we're not proposing for the Guideline, passing the test means we've implicitly required more capabilities than the guideline lists.16:15
markvoelkerSo, I'd say it's fine to propose them, we just need to do good due dilligence on them before approving.16:15
georgkyes, because of these reasons I´d like to explain the background of the interop tests and check if they can implement separate tests for the simple capabilities16:15
*** yamamoto has quit IRC16:17
markvoelkerThat sounds fine to me.  Do you have specific tests you're considering now?  We can dig into those a bit to see if any are ok if so....16:18
*** kgarloff has joined #openstack-meeting-316:18
georgkmarkvoelker: scenario or api tests?16:18
markvoelkerEither that exist today. =)  E.g. if there are scenario tests today we can look at them and see if they're testing anything outside of what's be proposed for inclusion.16:19
georgkok, I´ll do another round of review of the test cases and then send out my results by email.16:20
georgkis that ok?16:20
eglutethat would be great georgk16:21
eglutethank you16:21
markvoelker++16:21
georgkok, will do16:21
eglutethanks! anything else on this topic?16:21
markvoelkerIn other related news, I've been picking at some stuff around EPA support and Aodh this week while tracking down some problems in a lab.  Should have a patch up soonish for those.16:22
eglutetell us more markvoelker16:22
eglutewhat is this for?16:22
markvoelkerFor the NFV vertical program16:22
markvoelkerWe'd cited those as candidates for the first release16:23
markvoelkerI'm actually poking at some neutron QoS things too but I'll defer those for a later release I think.16:23
kgarloffSo we'll have aodh covered in the NFV program?16:23
eglutesounds good markvoelker thank you16:24
markvoelkerkgarloff: Well, at least we'll do a scoring exercise to see if anything merits inclusion.16:24
kgarloffmarkvoelker: great16:24
georgkone comment: in Denver, we said that the heat program is a candidate for a later point in time16:24
*** nseyvet has left #openstack-meeting-316:24
georgkbased on the fact that heat is used quite extensively in NFV, I was wondering if we should consider this also for inclusion16:24
kgarloffgeorgk: heat was discussed to be an addon program for platform ... should it be in NFV-base?16:25
georgkyes, like making the heat add-on also a component of the NFV program16:26
markvoelkergeorgk: I think the main rationale for waiting on it was twofold: 1.) we were going to work on Heat as an add-on program first, and 2.) there's some limbo around tests for Heat right now while the TC sorts out opinions on where to put tests...they'd been asked int he past to move them into tempest, now that may not be as much a thing (or it yet might)16:26
markvoelkerSo basically, I think the idea was to get an add-on program built for Heat and then make that part of the NFV vertical.16:26
georgkmarkvoelker: ok, fine with me16:27
markvoelkerNothing stopping us from doing them separately though, if we want...just seemed a bit duplicitous. =)16:27
kgarloffWe see significant heat usage on our public cloud (outside of NFV), so I agree that heat matters16:27
georgkok, so one thing at a time. sounds reasonable16:28
egluteok, anything else on this topic?16:29
eglute#topic Microversions16:29
*** openstack changes topic to "Microversions (Meeting topic: interopwg)"16:29
eglutehogepodge any updates?16:29
hogepodgeeglute: none, this work is stalled out with me prepping for the summit and KubeCon16:30
eglutecool, no worries16:30
eglute#topic  2018.02 guideline16:30
*** openstack changes topic to "2018.02 guideline (Meeting topic: interopwg)"16:30
eglutemarkvoelker i think neutron is the only one missing16:30
markvoelkerHah...got so wrapped up in the NFV stuff that I forgot to deal with that over Thanksgiving. =)  Ok, I'll add that to my queue for this week.16:31
*** psachin has quit IRC16:31
markvoelkerI'm actually not sure I'll end up proposing anything though.16:31
*** mugsie has joined #openstack-meeting-316:31
eglutemarkvoelker thank you! yeah, if you confirm no changes that works too16:31
markvoelker(other than cleaning up the comments in the working doc about subnet pools since we actually added those)16:32
egluteanything on the next guideline?16:32
*** skarlsson has quit IRC16:33
eglutecool16:33
eglutethere is a board meeting next week16:33
eglutei will inform the board that the next guideline will be in february16:33
egluteif there are any other updates i should announce, let me know16:33
eglute#topic Add-on programs16:33
*** openstack changes topic to "Add-on programs (Meeting topic: interopwg)"16:33
egluteso there is a patch to add tc:approved release tag for designate https://review.openstack.org/#/c/521587/16:34
eglutelast meeting we ran out of time to fully discuss this16:35
mugsieit is a simple step for the trademark program to actually add designate - the TC has to have blessed it16:36
mugsiethe other programs that were on the add on list were already in that tag afaik16:36
* markvoelker is happy to see this and expects the measure to pass16:37
eglute+116:37
egluteany other comments on the add on programs?16:37
eglutethere is also a testing patch:16:38
eglute#link https://review.openstack.org/#/c/521602/16:38
eglutethanks markvoelker for commenting on it16:38
*** psachin has joined #openstack-meeting-316:39
eglutethat one seems to be more for TC to decide16:39
markvoelkerOthers feel free to chip in too...the TC seems a bit divided on this at the moment, so your opinions and explanations of how things work in practice would be welcome I'm sure.16:40
egluteok i will respond later today, but i am in agreement with you16:40
mugsieyeah, we had some discussion in the RefStack meeting yesterday as well16:40
eglutei need to re-read all the comments again16:40
mugsiemy problem is some programs relying on a different interface, and the potential for breakage16:40
eglutemugsie what was the consensus in the refstack meeting?16:41
mugsiealong with the need for increased review quality16:41
mugsieeglute: none :(16:41
markvoelker#link http://eavesdrop.openstack.org/meetings/refstack/2017/refstack.2017-11-28-17.02.html Refstack meeting logs16:41
egluteok... I will respond to that patch. thank you markvoelker16:42
toskyduring the meeting I pointed out that the breakage that happened in the past (which was reverted) was more an exception16:42
egluteok16:42
egluteas for the proposed patch, i am ok with #2 or #3, I always liked #316:43
egluteeveryone, please review and comment #link https://review.openstack.org/#/c/521602/16:44
egluteany other discussion about it here?16:44
mugsieeglute: what would your pushback for #1 be?16:45
markvoelkerI am a little interested in how the mechanics would play out for keeping things in a central repo, but I can comment on that once I get caught up with all the comments from while I was away16:45
*** psachin has quit IRC16:45
eglutemugsie i think having only option #1 is limiting. I think we should be a bit more flexible when it comes to test location. If a project has all its tests in a separate plugin already, making them move seems to be busy work16:48
eglutebut i need to catch up with all the comments as well16:48
mugsiecool - I have a feeling this one will drag out a bit16:48
eglutethank you for proposing the patch, I think it is great discussion and was much needed16:50
markvoelkerThere have also been some concerns raised in the past about whether things like add-on programs were really "in scope" for tempest and whether QA would be able to handle all these tests...I think Andrea voiced those concerns in the review IIRC.16:50
toskythat's the reason why tests for non-"core" components moved outside tempest.git16:50
mugsiemarkvoelker: "in scope" for tempest is something that can be changed16:50
markvoelkerSure, but reviewer bandwidth is more difficult to change. =)16:51
mugsieit is 6 tests from us, I am not sure how many tests heat have but I cannot imagine it is huge16:51
mugsiebut, the discussion should be on the patch, so we have it recorded :)16:51
*** MarkBaker_ has quit IRC16:51
markvoelker++16:51
eglute++16:52
egluteeveryone, please comment on the patch16:52
*** marios has quit IRC16:52
egluteif nothing else on this, we can return to the hardest problem of all16:52
eglutenaming16:52
eglute#cycle name16:52
eglute#topic cycle name16:52
*** openstack changes topic to "cycle name (Meeting topic: interopwg)"16:52
hogepodgeThe one hardest problem, naming things and off-by-one errors16:53
eglutereminder, this is just for interop cycle name and really only affects the name of ehterpad mostly :)16:53
eglutewe have 5 suggestions right now16:53
eglutehttps://etherpad.openstack.org/p/InteropVertigo.2116:53
egluteplease everyone add your votes16:54
egluteright now Whistler is winning by 50%16:54
georgk:-)16:54
egluteok, if no other votes, whistler it is!16:55
eglute#topic open agenda16:55
*** openstack changes topic to "open agenda (Meeting topic: interopwg)"16:55
eglutewe still have 5 minutes, anything else that we need to discuss?16:55
markvoelkerQuick note on PTG for those who didn't see it: https://twitter.com/tcarrez/status/93579888346843136216:56
egluteis that a soccer stadium?16:56
kgarloffWhaoh!16:56
markvoelkerMore rugby nowadays, I think?  But yeah.16:57
hogepodgePlease let me know if you plan on attending.16:57
mugsieeglute: I wouldn't call it a soccer stadium when you are here ;)16:57
eglutemugsie yes, i grew up playing soccer16:57
mugsieIt is a gealic football stadium16:57
hogepodgeI have to respond to the PTG survey requesting resources. General head count and time needed.16:57
eglutemugsie i mean football16:57
markvoelkerhogepodge: I'm planning to be there.16:57
kgarloffNice for us Europeans16:57
mugsieIt is a cool venue16:58
markvoelkerAnd will be happy to use a friendly game of football or rugby to settle tie votes...16:58
eglutei think i will too.16:58
eglutethanks everyone!16:58
eglute#endmeeting16:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:58
openstackMeeting ended Wed Nov 29 16:58:41 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-11-29-16.01.html16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-11-29-16.01.txt16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-11-29-16.01.log.html16:58
mguineyhave a good week!16:59
*** chyka has joined #openstack-meeting-317:01
*** Sukhdev has quit IRC17:06
*** tosky has left #openstack-meeting-317:06
*** MarkBaker has joined #openstack-meeting-317:21
*** e0ne has joined #openstack-meeting-317:44
*** sambetts is now known as sambetts|afk17:48
*** cshastri has joined #openstack-meeting-317:57
*** MarkBaker has quit IRC17:58
*** salv-orl_ has quit IRC17:59
*** salv-orlando has joined #openstack-meeting-317:59
*** salv-orlando has quit IRC17:59
*** ansmith has quit IRC18:02
*** MarkBaker has joined #openstack-meeting-318:03
*** salv-orlando has joined #openstack-meeting-318:03
*** iyamahat has quit IRC18:05
*** cshastri has quit IRC18:06
*** lhx_ has quit IRC18:08
*** yamahata has quit IRC18:09
*** MarkBaker has quit IRC18:14
*** coolsvap has quit IRC18:18
*** iyamahat has joined #openstack-meeting-318:26
*** iyamahat_ has joined #openstack-meeting-318:34
*** iyamahat has quit IRC18:34
*** salv-orlando has quit IRC18:36
*** salv-orlando has joined #openstack-meeting-318:36
*** salv-orlando has quit IRC18:41
*** tssurya_ has joined #openstack-meeting-318:42
*** yamahata has joined #openstack-meeting-318:45
*** david-lyle has joined #openstack-meeting-318:45
*** shuyingya has quit IRC18:53
*** iyamahat_ has quit IRC18:54
*** david-lyle has quit IRC18:54
*** iyamahat has joined #openstack-meeting-318:54
*** diablo_rojo has quit IRC18:55
*** diablo_rojo has joined #openstack-meeting-318:55
*** Sukhdev has joined #openstack-meeting-318:59
*** david-lyle has joined #openstack-meeting-319:01
*** david-lyle has quit IRC19:02
diablo_rojoRunning a little late, but we will be having a storyboard meeting!19:06
*** tssurya_ has quit IRC19:06
*** tssurya_ has joined #openstack-meeting-319:07
*** iyamahat has quit IRC19:07
*** iyamahat has joined #openstack-meeting-319:08
*** slaweq has joined #openstack-meeting-319:10
*** tssurya_ has quit IRC19:12
*** sgrasley1 has quit IRC19:16
*** slaweq has quit IRC19:17
*** slaweq has joined #openstack-meeting-319:18
*** david-lyle has joined #openstack-meeting-319:21
*** slaweq has quit IRC19:22
*** ociuhandu has joined #openstack-meeting-319:32
*** david-lyle has quit IRC19:34
*** david-lyle has joined #openstack-meeting-319:35
*** ociuhandu has quit IRC19:36
*** salv-orlando has joined #openstack-meeting-319:37
*** salv-orlando has quit IRC19:42
*** rdopiera has joined #openstack-meeting-319:51
*** david-lyle has quit IRC19:53
ying_zuo#startmeeting horizon20:00
openstackMeeting started Wed Nov 29 20:00:29 2017 UTC and is due to finish in 60 minutes.  The chair is ying_zuo. 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
ying_zuoHi everyone o/20:00
rdopierao/20:00
e0nehi20:00
ying_zuo#topic Queens-2 milestone20:01
*** openstack changes topic to "Queens-2 milestone (Meeting topic: horizon)"20:01
ying_zuoI plan to tag the release next Tuesday or Wednesday20:01
ying_zuohere are the tickets planned for this milestone20:02
ying_zuo#link https://launchpad.net/horizon/+milestone/queens-220:02
ying_zuo#topic Fetch resources in parallel discussion (again) (e0ne)20:03
*** openstack changes topic to "Fetch resources in parallel discussion (again) (e0ne) (Meeting topic: horizon)"20:03
e0neI want to get some feedback on this proposal20:03
e0ne#link http://lists.openstack.org/pipermail/openstack-dev/2017-October/124129.html20:03
*** david-lyle has joined #openstack-meeting-320:04
e0nethere're number of patches on the review and some are already merged20:04
e0nebut we still don't have a decision how to go forward this futurist20:04
*** cshen_ has joined #openstack-meeting-320:05
ying_zuoare we discussing about a specific patch?20:06
e0neying_zuo: you can find patches in scope of https://blueprints.launchpad.net/horizon/+spec/fetch-resources-in-parallel20:07
e0nebut we need a general agreement how to deal with futurist in horizon20:07
rdopierae0ne: what I'm concerned with is how this works with the web servers, such as apache, which do their own thread management20:08
e0nerdopiera: for now, we use python threads and allow them in mod_wsgi config20:08
e0nerdopiera: my proposal is to use greenthreads instead20:08
rdopierae0ne: you don't need stackless python for that?20:09
e0nerdopiera: no, just eventlet + futurist(it's already in our requirements.txt)20:09
ying_zuoamotoki asked for the performance data on the patch/blueprint https://review.openstack.org/#/c/426493/20:10
*** shuyingya has joined #openstack-meeting-320:11
e0neying_zuo: there are performance testing results in my email20:11
e0neamotoki asked it before I sent a message to openstack-dev20:11
ying_zuoI see. can you reply there with the link?20:11
e0ne#link https://docs.google.com/spreadsheets/d/14zDpdkPUfGDR_ZycaGUoT64kHsGi1gL9JOha8n5PVeg/edit?usp=sharing20:12
e0neI added the link ^^ to the blueprint20:12
amotokihi20:14
amotoki, i succeeded to wake up earlier20:14
amotokie0ne: do you have some data without futurist too?20:14
ying_zuogood morning :)20:14
*** tellesnobrega has left #openstack-meeting-320:15
e0neamotoki: good morning! I hope, you enjoyed your morning coffee20:15
e0neamotoki: no, why do we need it?20:15
*** shuyingya has quit IRC20:15
*** tellesnobrega has joined #openstack-meeting-320:15
e0neamotoki: futurist just a wrapper over threading libraries20:15
amotokiin my understandng, we first need to discuss futurist (or parallel loading) is needed or not.20:16
e0neamotoki: I hope, everybody agrees that parallel API calls are better for our case20:16
amotokieven though it speed up loading time per user, i am not sure how this affect totally.20:17
e0neamotoki: I don't get your point20:17
amotokiin general, web server serves several requests in parallel.20:17
cshen_do we have benchmark for the current used libraries?20:18
amotokitotal throughput and response time per request is a different thing.20:18
e0necshen_: yes, there as a link above20:18
amotokii am wondering futurist introduces how much additional overhead.20:19
rdopieraif I remember correctly, we started the whole AngularJS rewrite to get parallel requests20:19
e0neamotoki: there is almost no overhead for horizon20:19
e0nerdopiera: yes, but I propose to speed-up our server-side code too20:20
rdopierae0ne: sure20:20
ying_zuoit would be good to get some data on how much performance gain this will give20:21
e0ne#links https://github.com/openstack/horizon/blob/04894a0858adda0ae161d9ac1f1a8da017ba1c74/openstack_dashboard/dashboards/project/instances/views.py#L12220:21
e0ne^^ that's how we use futurist now20:21
*** slaweq has joined #openstack-meeting-320:21
amotokiokay, so have we agreed introducing parallel loading using futurist as a baseline?20:21
e0ne@ying_zuo: did you see my spreadsheet with tests results?20:22
cshen_e0ne, how many API calls were in your benchmark?20:22
e0neamotoki: I hope so,,,20:22
amotokianyway some baseline performance data (without parallel loading) would be useful20:22
rdopieraI wonder if we should have settings like max_workers exposed in the settings, instead of hardcoded...20:22
ying_zuoeone: yes, I mean compare with without parallel20:22
rdopierain particular, to give the admins the ability to limit or even disable parallel loading20:23
e0necshen_: it was 3 API calls20:23
amotokirdopiera: are talking about max_workers of ThreadPoolExecutor ?20:23
e0nerdopiera: I still doesn't understand why do we need to have this configurable20:24
rdopieraamotoki: I'm not sure about how that particular option works, I'm thinkning about the ability to limit the number of concurrent requests, not sure how we would do it exactly20:24
e0neying_zuo: I don't have such data now, but I'm sure it will be slower (I did some testing in the past)20:25
rdopierae0ne: with certain networks settings you don't want to have too many transfers at once20:25
rdopierae0ne: that is also why web browsers only fetch up to 4 resources at a time20:26
*** Sukhdev has quit IRC20:26
e0nerdopiera: it's not true for current web browsers20:26
rdopierae0ne: the option is there20:26
*** salv-orlando has joined #openstack-meeting-320:27
e0nerdopiera: seriously, if your production network and APIs don't allow 3-4 request in parallel, it's not a problem of horizon20:27
rdopierae0ne: seriously, if horizon doesn't work at customer's site and there is no option to make it work, it is a problem of Horizon20:28
e0neI can't argue20:28
rdopierae0ne: you are making assumptions about how horizon is being used that are not necessarily true20:28
e0nerdopiera: I agree20:29
rdopieraI'm also thinking that the ability to limit it to 1 request at a time may be useful to help debug race conditions20:29
e0negood point20:29
rdopieraespceially when there are multiple requests to the same service20:30
rdopieraor to services that use the same resource20:30
e0nebut we won't have race conditions with only 1 request20:30
rdopieraexactly -- so if the problem goes away when you limit it to 1 request, you know it's a race condition :)20:30
e0ne:)20:31
rdopieraso far most use cases are for reading, so it's not very risky20:31
rdopierabut we might at some point also use it for requests that modify data20:31
ying_zuoso we should make that configurable20:32
ying_zuoanything else on this topic?20:32
e0neying_zuo: do we have any decision on this topic?20:33
ying_zuoThreadPoolExecutor is being used in horizon now, do you want to change it to something else?20:33
amotokii am not sure max_workers=1 and serial API calls are same or not. Does max_workers=1 create one new thread?20:34
e0neamotoki: in a current case - yes20:34
e0neI mean with futurist20:34
amotokiin such case, does futurist execute each submit() one by one in a single worker?20:35
e0neit does, AFAIR20:36
*** iyamahat has quit IRC20:36
amotokithanks20:37
e0nenp20:38
amotokiregarding ying_zuo's question, I am not sure which is betetr ThreadPoolExecutor or GreenThreadExecutor20:39
e0neI prefer GreenThreadExecutor20:40
e0neit's faster and doesn't require additional webserver configuration20:41
rdopierait also uses less memory20:41
e0neying_zuo: I propose to switch to GreenThreadExecutor20:41
e0nerdopiera: +120:41
*** tssurya_ has joined #openstack-meeting-320:42
rdopierahowever, it does monkey-patch the system functions, iirc20:42
rdopierato add greenthread support to them20:42
amotokiyes, eventlet assumes related modules are monkey-patched.20:42
rdopierabut I think it has been around long enough for most bugs to be shaken out20:43
e0nerdopiera: +120:43
*** iyamahat has joined #openstack-meeting-320:43
ying_zuoe0ne: please update the blueprint for your proposal20:44
e0neying_zuo: ok, I'll do20:44
ying_zuothanks. we can continue the discussion there20:44
ying_zuo#topic Merge openstack-auth (amotoki)20:45
*** openstack changes topic to "Merge openstack-auth (amotoki) (Meeting topic: horizon)"20:45
e0neying_zuo: thanks20:45
ying_zuo#link https://blueprints.launchpad.net/horizon/+spec/merge-openstack-auth20:45
ying_zuo#info Upgrade issue of openstack_auth in pip environment20:45
ying_zuohere's some information from amotoki:20:45
ying_zuohttps://www.irccloud.com/pastebin/AaEbFVsG/20:45
*** david-lyle has quit IRC20:45
amotokiit only affects operators who use pip directly to install horizon.20:46
ying_zuowould be good to have this information on the release note20:47
amotokiperhaps it does not affect distro users. venv/container users are not affected too20:47
amotokii assume most operators with venv replaces venv when upgrading :)20:48
rdopierathe whole change also affects packagers20:48
rdopieraI propose to let them know about such changes in the future, as they might not be following everything all the time20:48
e0nerdopiera: +120:49
ying_zuothere was an email a while back20:49
rdopieraI missed it completely and so did zigo20:49
rdopierait's our fault, of course20:50
ying_zuorelease note will be a good place for this :)20:50
zigordopiera: Missed what?20:50
zigoMerge of openstack-auth ?20:50
rdopierazigo: the merging of openstack-auth20:50
rdopierayeah20:50
zigoRight.20:50
zigoI'm fine with it, really.20:50
zigoOne less package to maintain ! :)20:50
rdopierayeah, it's just the kind of change that would be nice to be coordinated20:50
amotokithe mail was http://lists.openstack.org/pipermail/openstack-dev/2017-July/119731.html20:51
rdopieraok, that is exactly the kind of information that I meant, I withdraw my statement20:51
zigoWhat concerns me more is django 2.x, Horizon IMO needs to support that ASAP.20:51
rdopierait's my fault I missed it20:51
e0nezigo: I think, we can start work on if right after release20:52
*** shuyingya has joined #openstack-meeting-320:52
zigoe0ne: That's already too late for Debian at least.20:52
e0ne:(20:52
zigoI'm not sure when, but "soon" django 2.x will replace 1.11 in Sid. When this happens, horizon wont work anymore in Debian.20:53
amotokibut isn't django 2.x released yet?20:53
e0neI didn't test horizon with django2.020:53
e0neamotoki: it's not released yet20:53
e0nezigo: oh.. it will be painfull for anybody who doesn't support python3 and django 2.0+20:54
e0ne5mins reminder20:55
zigoThere's the rc1 already.20:55
ying_zuoI thought django 1.11 is LTS so we are good for a while20:55
*** VW_ has joined #openstack-meeting-320:55
e0neI thinks, it's a good idea to add non-voting job with django 2.020:55
amotokiDoesn't Debian give django app maintainers time to catch up their apps after the release?20:55
*** shuyingya has quit IRC20:56
cshen_django 2.0 seems to be not a LTS version.20:56
ying_zuowe will need a blueprint and a volunteer20:57
e0neying_zuo: you're right, 1.11 will be supported until 202020:57
e0neying_zuo: I'll file a blueprint and propose a patch with non-voting job20:57
e0necshen_: +120:57
amotokihttps://www.djangoproject.com/weblog/2015/jun/25/roadmap/20:57
e0ne#link https://www.djangoproject.com/weblog/2015/jun/25/roadmap/20:57
*** salv-orlando has quit IRC20:58
ying_zuo:)20:58
cshen_django 2.2 will be a LTS version, which is scheduled to be released in 2019.20:58
amotokireturning back to django-openstack-auth topic, I need volunteers to finish remaining works20:58
e0nerobcresswell: are you around? :)20:58
amotokithere are a lot of remaining works out side of horizon repos.20:58
*** VW__ has joined #openstack-meeting-320:58
amotokirequirements, devstack, project-config......20:59
*** VW has quit IRC20:59
e0neunfortunately, I don't have time for it:(. there are still some bugs in my queue20:59
rdopieraI'm finishing up with downstream pike, hopefully should have some time now21:00
ying_zuowe are running out of time. If anyone has some bandwidth, please pick up the todos in the blueprint21:00
*** mriedem has joined #openstack-meeting-321:00
*** pcaruana has quit IRC21:00
*** VW_ has quit IRC21:00
ying_zuothanks everyone for joining21:00
amotokii am not sure i have covered all items..... cross-check is required21:00
ying_zuo#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Wed Nov 29 21:00:49 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-11-29-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-11-29-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-11-29-20.00.log.html21:00
dansmith#startmeeting nova_cells21:00
openstackMeeting started Wed Nov 29 21:00:54 2017 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
e0nerdopiera: the same for me. we're working on downstream pike  too :)21:00
mriedemo/21:01
tssurya_o/21:01
melwitto/21:01
dansmith#topic bugs21:01
*** openstack changes topic to "bugs (Meeting topic: nova_cells)"21:01
dansmithso, belmiro reported an issue recently,21:01
dansmithalthough not via a bug21:01
dansmithand I put up a patch:21:01
dansmithhttps://review.openstack.org/#/c/523187/21:01
mriedemah i was going to ask for a recap of this21:01
dansmithhe said that worked for him, so I probably need to get him to file a bug and then clean that up so we can merge/backport it21:01
dansmithI guess we can't really send it back to newton, although that's where he wants it21:02
mriedemthis is also specific to how he's doing the api db setup per child cell yes?21:02
dansmithyes, although this is the right thing to be doing anyway I think21:02
tssurya_mriedem : yes21:02
mriedemso we're deleting the build request here so that it doesn't get confused at the top when listing instances?21:03
dansmithyeah21:03
dansmithotherwise it obscures looking for the real instance21:03
dansmithsince the mere presence means "don't even look for an instance"21:03
*** rdopiera has left #openstack-meeting-321:03
mriedemand if you're doing global placement with a single api db, we'd likely get the build request not found, which we ignore21:03
mriedemi know nectar said they are doing global placement, not per child cell21:04
*** salv-orlando has joined #openstack-meeting-321:04
dansmithright, because the compute api in the lower cell would have already done it21:04
*** david-lyle has joined #openstack-meeting-321:04
mriedemok21:04
dansmithyeah and I don't think godaddy was far enough along to have thought through this21:04
mriedemgodaddy was waiting to see how everyone else (2 of them) had done it21:04
dansmithI dunno how many cells they have, but I'm kinda assuming they're somewhere between cern and nectar in terms of numbers21:04
dansmithheh, so that worked out well for them21:04
dansmithtwo examples, two answers21:04
*** sgrasley1 has joined #openstack-meeting-321:05
mriedemi was also going to ask if we were going to push patches up for the issues cern runs it, so i'm happy to see we are21:05
*** cshen_ has quit IRC21:05
dansmithyeah, I think we should for sure21:05
mriedemi figured we'd at least need somewhere/somethign to track patches people need to transition from v1 to v221:05
dansmithI'd rather it be integrated when and where possible21:05
dansmithso I assume you're cool with this back to ocata but not newton?21:05
mriedemtssurya_: can you follow up with belmiro to open a bug?21:05
mriedemdansmith: yeah21:05
tssurya_mriedem : yes of course21:06
dansmithtssurya_: and just comment on the patch with the bug number or something21:06
*** cshen_ has joined #openstack-meeting-321:06
dansmithtssurya_: you could open it too, doesn't have to be belmiro21:06
tssurya_dansmith : yes , I will follow this up21:06
dansmithcool, thanks21:06
dansmithanything else on this or other bugs?21:06
tssurya_not from me21:07
*** d0ugal has quit IRC21:07
mriedemi don't have any bugs in mind21:07
dansmith#topic open reviews21:07
*** openstack changes topic to "open reviews (Meeting topic: nova_cells)"21:07
dansmithso the big one still open here is ed's alternates patches,21:07
dansmithwhich I honestly haven't looked at much since sydney for various reasons21:07
dansmithsome good reasons, so not so good ones21:07
mriedemi made it about halfway,21:08
melwittsame, it's on my todo for today or tomorrow21:08
dansmiththere's also melwitt's fixtures cleanup, which I think I have uncommitted comments on,21:08
mriedemjay was -1 on something in the middle so thta's where i stopped b/c ed was on vacation21:08
dansmithyeah21:08
*** sgrasley1 has quit IRC21:08
dansmithany other open reviews we need to be highlighting here?21:09
*** sgrasley1 has joined #openstack-meeting-321:09
mriedemkinda21:09
mriedemjust a mention of https://review.openstack.org/#/c/517273/2521:09
mriedemi brought this up the other night,21:09
mriedempaging migrations across cells,21:09
dansmithoh right21:09
dansmithugh21:09
mriedemhe changed it from PS21 to PS25,21:09
mriedemand he's moving in what i think is the right direction, just in the wrong way21:09
melwittI have a patch up to remove old quotas code, not directly related to cells but related to the quota changes from last cycle https://review.openstack.org/51168921:09
mriedemso i've dumped more comments in there,21:09
mriedemi think he basically wants to page like we used to do for instances, and then just simple merge sort the results at the end21:09
mriedemno scatter/gather fanciness21:10
dansmiththe scatter gather is easier than doing it manually because it handles iterating cells for you21:10
dansmithand does it in parallel, so not sure there's any benefit if you're going to merge at the end21:10
mriedemthe other night when i brought this up,21:11
mriedemyou seemed to agree that we didn't need the overhead of the stuff used for instance_list.py21:11
dansmithyeah, right, but the scatter/gather thing is not instance_list,21:11
dansmithit's just the bit in context.py which iterates cells for you21:11
dansmithmaybe we're confusing terminology21:12
dansmithhe _should_ use the context.scatter_gather_all_cells() thing21:12
mriedemhe's using scatter/gather to find the cell that the marker is in21:12
mriedemand then iterating the cells starting at that cell, i think21:12
mriedemnot even probably, which is another issue here21:12
dansmithnot sure why that helps really21:12
*** lyan has quit IRC21:13
dansmithalso, since this is new, we could do something smarter about the marker id so we can avoid doing the two-stage marker lookup right?21:13
mriedemlike, encode the cell id in the marker?21:13
dansmithyeah21:13
mriedemwe could,21:14
mriedemthat means some custom marker/paging code in the rest api handler, which is different from how everything else builds the next links21:14
dansmithor include a next-page: <url> thing in the response and you just call that, so we can change it over time21:14
dansmithyep, indeed21:14
dansmithanyway, if we don't change that, then he just has to look up the marker and do the thing, but I would scatter both times, personally21:15
dansmithno reason not to21:15
mriedemi have to say,21:15
dansmithyou wish for death?21:15
dansmithyeah me too21:15
mriedemi'm a bit confused on how we'd get the marker correct once the results are sorted, but i haven't thought through it all21:16
mriedemlike i know this is working for instances21:16
dansmithwell, you still have to do the local marker thing per cell21:16
mriedeme.g. if i page across cell1 to cell2 and my marker is in cell2 before sorting,21:16
mriedembut then sort and my marker is in cell1, its weird21:16
dansmiththat's why encoding something more in the marker id would let us avoid that21:17
mriedemhmm, ok he dropped the local marker stuff he had in PS2121:17
dansmithbecause you have to look up the marker globally by uuid, then look up the marker per cell by >=$sort_field, and then use that as your marker= to the actual list call21:17
dansmithif we encoded the marker uuid, cell id and the sort key from the global marker in the result, then we wouldn't have to do all that and could restart the paginated query right away21:18
dansmithanyway, let's not design it here, we can discuss elsewhere21:19
*** lyan has joined #openstack-meeting-321:19
dansmithany other reviews to highlight?21:20
mriedemnot me21:20
dansmith#topic open discussion21:20
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"21:20
*** raildo has quit IRC21:20
dansmithso I had a thing to point out here, but I forgot what it was21:20
melwitthmm21:21
dansmithanyone else got anything?21:21
mriedemnope21:21
melwittnay21:22
tssurya_nope21:22
dansmithokie doke21:22
dansmith#endmeeting21:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:22
openstackMeeting ended Wed Nov 29 21:22:23 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:22
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-11-29-21.00.html21:22
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-11-29-21.00.txt21:22
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-11-29-21.00.log.html21:22
*** mriedem has left #openstack-meeting-321:23
*** lyan has quit IRC21:33
*** ccamacho has quit IRC21:33
*** sgrasley1 has quit IRC21:40
*** sgrasley1 has joined #openstack-meeting-321:41
*** sgrasley1 has quit IRC21:47
*** cshen_ has quit IRC21:48
*** ccamacho has joined #openstack-meeting-321:50
*** lyan has joined #openstack-meeting-322:10
*** MarkBaker has joined #openstack-meeting-322:15
*** slaweq has quit IRC22:32
*** slaweq has joined #openstack-meeting-322:34
*** etingof has quit IRC22:37
*** slaweq has quit IRC22:39
*** shuyingya has joined #openstack-meeting-322:41
*** caboucha has quit IRC22:41
*** georgk has quit IRC22:43
*** lyan has quit IRC22:43
*** shuyingya has quit IRC22:46
*** e0ne has quit IRC22:49
*** e0ne has joined #openstack-meeting-322:50
*** e0ne has quit IRC22:51
*** e0ne has joined #openstack-meeting-322:51
*** e0ne has quit IRC22:51
*** e0ne has joined #openstack-meeting-322:52
*** e0ne has quit IRC22:52
*** e0ne has joined #openstack-meeting-322:53
*** e0ne has quit IRC22:53
*** e0ne has joined #openstack-meeting-322:54
*** e0ne has quit IRC22:55
*** e0ne has joined #openstack-meeting-322:55
*** e0ne has quit IRC22:55
*** etingof has joined #openstack-meeting-322:56
*** ccamacho has quit IRC23:04
*** d0ugal has joined #openstack-meeting-323:04
*** shuyingya has joined #openstack-meeting-323:22
*** salv-orlando has quit IRC23:22
*** salv-orlando has joined #openstack-meeting-323:22
*** VW__ has quit IRC23:24
*** VW has joined #openstack-meeting-323:25
*** bobh has quit IRC23:25
*** bobh has joined #openstack-meeting-323:26
*** pbourke has quit IRC23:26
*** VW_ has joined #openstack-meeting-323:26
*** salv-orlando has quit IRC23:27
*** shuyingya has quit IRC23:27
*** VW has quit IRC23:27
*** pbourke has joined #openstack-meeting-323:28
*** VW_ has quit IRC23:29
*** VW has joined #openstack-meeting-323:30
*** bobh has quit IRC23:30
*** gmann_afk is now known as gmann23:31
*** VW has quit IRC23:34
*** marst has quit IRC23:49
*** bobh has joined #openstack-meeting-323:53
*** absubram has joined #openstack-meeting-323:55

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